Access & Terminal Server

[Guest]

I have several client that connect to my Access database through Terminal
Server. The problem I am having is when they lose their connection, they are
corrupting my database. Are there any provisions in Terminal Server to help
this problem?

 

[Guest]

Make sure that your database is split into data tables and an application
front-end. Use a separate folder for each user and place a copy of the linked
front-end in each folder. Users will now have a personal copy of the
front-end.

I've been running that way for almost 2 years now with 5 to 8 users and
haven't corrupted the database even once. Never have multiple users directly
connected to the same file. That's asking for trouble.
--
Arvin Meyer, MCP, MVP
Microsoft Access
Free Access downloads
http://www.datastrat.com
http://www.mvps.org/access

 

[Albert D.Kallal]

When users drop a connation, that should not be a problem at all.

When users re-connect, they are resumed back to the same screen.

If you have a "nasty" administrator who is force logging off (blowing out
the users) when they are connected to the database, then it is your
administrator of the system that is causing the corruption.

Simply tell the admin to stop blowing out those users that don't log off.
Simply have those users re-connect...they will be retuned to exactly where
they left off in the application...and have them exit correctly.....

A dropped connection in terminal server will NOT corrupt a ms-access file.
It is possible that some TS settings are killing a person who does not log
off, so, check those settings.

One of the great reasons why we use TS is that a dropped connection WILL NOT
damage the file....