Splitting a database to an FTP server running Linux

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I have a split database (only 8 users) with one Windows XP machine holding the back-end portion of the database. It works just fine. I want to migrate the shared tables to an FTP server that runs on Linux, so that a few more people will have access (no pun intended) and security can be improved.
However, the Link Table Manager refuses to change the data path - error message "Invalid File Name". The shared tables copied to the FTP server easily and are visible outside the database.
Can a person run the back-end on an FTP server? ANY HELP is greatly appreciated.
 
Dave said:
I have a split database (only 8 users) with one Windows XP machine holding
the back-end portion of the database. It works just fine. I want to migrate
the shared tables to an FTP server that runs on Linux, so that a few more
people will have access (no pun intended) and security can be improved.
However, the Link Table Manager refuses to change the data path - error
message "Invalid File Name". The shared tables copied to the FTP server
easily and are visible outside the database.
Can a person run the back-end on an FTP server? ANY HELP is greatly
appreciated.

FTP = file transfer protocol

You can't run any kind of file share system across a network via FTP. When
you split a mdb file, you simply have a file sitting in a folder. To open
that file you need a network protocol that supports file reading, and file
writing. In other words...a simple file transfer protocol such as FTP is not
even close to working alike a regular shared folder on a network.

So, with Linux you can simply use what is called Samba. Samba is simply
windows networking that runs on the server. And, once setup, you can then
simply use the linked table manager and browse to the back end like you
always did. You get no more connectivity then what windows offers.

Now, you don't want to confuse the issue of a local office network (and that
back end can be on your windows xp box, or your Linux server). However,
trying to share, or access those files across the internet is a completely
different issue. So, I not sure why you hint, suggest or even think that
moving the shared mdb file from a windows box to a Linux box will improve
security? In both cases you will have to give users full rights to that
directory, and all users will need to be able via network neighbourhood
browse to that shared folder to link to. This process is not different if
use a windows box, or Linux and samba.

If you are talking about a wan/internet, then you would have to setup a VPN
(a virtual private network is windows networking ACROSS the internet..and
you need to use that in place of the simple FTP which only transfers a file.
Thus, you will see the one computer in new York, and the other computer in
be in LA, but both will appear in the network, and you MUST as usual be able
to browse to the back end to link to the mdb file.

However, the speed of the internet is about 100 times to slow to run a file
share across the internet anyway.

You can read the following and I explain the solutions/problems you have
when using a WAN.

http://www.attcanada.net/~kallal.msn/Wan/Wans.html
 
Many people think that Jet is a 'file based' system
rather than a 'client server' system, and that it 'brings
the whole file down'. Actually it is a 'file based client
server' system, and needs a 'file server' -- not an FTP
server. People have made FTP based ODBC drivers and
block storage device drivers for Windows, but last I
looked, I couldn't find one: interest in FTP based file
system emulation has been replaced with interest in
OSD/iSCSI/iSNS. In any case, unless file system emulation
emulates RECORD transfer and locking as well as FILE
transfer and locking, it will not work with Access and
Jet.

(david)

Dave said:
I have a split database (only 8 users) with one Windows XP machine holding
the back-end portion of the database. It works just fine. I want to migrate
the shared tables to an FTP server that runs on Linux, so that a few more
people will have access (no pun intended) and security can be improved.
However, the Link Table Manager refuses to change the data path - error
message "Invalid File Name". The shared tables copied to the FTP server
easily and are visible outside the database.
Can a person run the back-end on an FTP server? ANY HELP is greatly
appreciated.
 
Back
Top