That's good. I do beleive I may have found the resolution to the problem.
What I've found is that when the users are calling up drawings from out local
intranet, Adobe Acrobat Reader would open up to display the drawing. They
would then select the Print icon to print the drawing and the lockup would
occur quite often. Yesterday, in the preferences of the reader, I modified
the connection which was set to dialup connection at 56kb and changed it to
be a LAN connection which it is. I checked the event view on the Terminal
Server this morning and I don't see any events from last night, which in the
past I saw many events. I think this may have been the root cause. I will
monitor this for another day and if all goes well, this was it. I will
respond back to verify this.
Thank you!

"GBA" wrote:

isn't an Access issue per se....there is nothing in Access which knows that
one is using terminal services, so there is no setting or anything that one
could change.

whether terminal services or not terminal services; one should split an
Access db and establish a front end.mdb (FE) for each user. in a non
terminal services environment you put the FE on the PC of each user. in a
terminal services environment you put that FE in each users virtual space -
the exact instructions depend on the version and maker of your terminal
services...and so you will want their assist.....

"Kelly" wrote:

Hi, I'm running an Access database that's been running for 2 years without
problems. I have the backend on a Sequel2000 Server and never had any
problems with it. I now swapped out the computer with a thin client running
Terminal Services. I was using Access 2000 and the problem is that the thin
client access application keeps locking up. The mouse click seems to stop
working for the access application. Is there something special I must do to
use this database in a terminals service session?
I ended up making it an MDE thinking this would help, but it didn't seem to
change anything. I only have (2) users using the database, (1) being a PC and
the other a thin client. The PC doesn't have this problem.

Thank you,