Access over VPN

[alvechurchdata]

We've had a dozen users sharing an Access 97 database for the past five years. Each has the front end on their own PC linked to the back end on the server. Now we've got VPN installed and have found that only one person at a time can use the front end on the VPN server. Is this normal?

Geoff Franklin

http://www.alvechurchdata.co.uk

 

[jsteph]

I'd steer clear of sharing a front end, especially if there is local data (local to the f.e.) and/or dynamic object changes.

They should still copy the f.e. to the machine which they use to connect to the vpn, ie, their laptop or home machine.
--Jim

 

[alvechurchdata]

I'd steer clear of sharing a front end, especially if there is local data

I had a vague memory that it was a bad thing to do but I couldn't remember why.

They should still copy the f.e. to the machine which they use to connect to the vpn,

I'd agree that would be the ideal but they don't have that option on this site. The only VPN facility they've got is the ability to run terminal session on the server.

Geoff Franklin

http://www.alvechurchdata.co.uk

 

[jsteph]

If it's a terminal services session, then the front-end can be in the user's Desktop--assuming they all log in under a unique username.

If they're all logging into ts under a common name, then I'd change that--for security reasons alone it's a good idea, but also for the reasons here--they'd each get a unique Desktop where they'd have their own front-end copy.
--Jim

 

[Najemikon]

I run a database over terminal services with no problem at all. Although it is split, both the front & back ends are stored in a folder (not the desktop) on the server. We connect via RDP on the LAN or from outside the office on the Internet. Works a treat.

 

[alvechurchdata]

I run a database over terminal services with no problem at all.

Thanks for th ereassurance, I'm glad to hear it is possible. I'll try to get some more effort out of the folks who are responsible for the VPN. Their line at the moment is that it's an Access problem.

Geoff Franklin

http://www.alvechurchdata.co.uk

 

[Hap007]

Hi Geoff,

You got much good advice in the other answers.

The most important, have your admin set it up so each user logs on with there own unique copy of the frontend.

Also.
You mention that you are using Access97.
One of the reasons that Microsoft released Access 2000, was terminal services. Reason, Access97 had some system files that were shared, even on Terminal server.
So, I would advise you to move the Frontend to Access 2000 or later.

Good Luck,
Hap...

Access Developer

http://www.fcs-software.com/fcsaccessdev.html

Access based Add-on Solutions
Access Consultants forum

http://www.tek-tips.com/threadminder.cfm?pid=1121

 

[alvechurchdata]

[Access97 had some system files that were shared, even on Terminal server.]

Sorry to have taken so long getting back to you but that's how we solved it in the end. Every user now has their own shortcut in their own area on the server pointing to their own MySystem.mdw.

So, I would advise you to move the Frontend to Access 2000 or later.

It's a charity with volunteer users. They're hoping to get Office 2005 this year but some of their home users have machines which need to be upgraded first.

Geoff Franklin

http://www.alvechurchdata.co.uk