Access over a VPN

[Rick Exner]

I have been attempting to use an Office 2000 Access file
over a VPN. Access seems to be the most difficult Office
application to use in this way. When loading the file, I
usually get "delayed write failed," "Windows cannot find
(filename)", or "Network error" messages. Several times I
have corrupted the database when these errors occurred.

Are there any guidelines or tips for safely using Access
remotely in this way?

Thanks,
-Rick Exner

 

[Kevin3NF]

Other than don't do it? No. Not for .mdb files anyway. Access Data Projects
maybe, but I don't have that experience.

Access over VPN is a bad idea all the way around for the very reasons you
describe. Set up a terminal server instead. I have a client with this
setup and it works like a champ.

 

[Rick Exner]

Thank you for the tip. Pardon my ignorance, but what's
a "terminal server"? How does it work?
-Rick Exner

 

[Kevin3NF]

Terminal server is a utility built into Windows 2000 Server that allows
remote users to log in and work as if they are sitting at a workstation in
the local network. Multiple users can log on at once, each seeing their own
desktop, icons, etc.

There are some licensing issues, and installing programs has to be done a
certain way, but it is a reasonable setup. As I mentioned, I have a client
successfully using it now, and I use it to monitor that client's network
from my house.

 

[tpherr]

It's not Access over a VPN that is the issue: it is likely
the speed of the connection. is the connection done with
broadband or dialup? I have a 200M Access Db that users
open on a broadand P with no issues.

Tim

 

[Albert D. Kallal]

I have some tips at the end of the following article on how to fix this
problem:

http://www.attcanada.net/~kallal.msn/Wan/Wans.html

 

[Kevin3NF]

Nice article....