Arvin - Thank you,
I will take your advice and see if there is something else going on with the
server. I'm noticing that the problem with Access buttons not working is now
godn and the events seem to be relating to the HP printer driver - it looks
like anyway. I will report back my findings.

Thank you!

"long" wrote:


"Arvin Meyer [MVP]" дÈëÏûÏ¢ÐÂÎÅ:uWpLBEIXKHA.1372@TK2MSFTN GP02.phx.gbl...
"Kelly" wrote in message
...
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.

With terminal services, you must have a copy of the front-end for each
user. I usually put a folder on the machine with the front-end in it, and
when the users logs in, (s)he is directed to that folder and not permitted
to go anywhere else. I have never had a problem with multiple users some
with local LAN front-ends, and others on a terminal server (and still
others with an asp front end) The web server and database were on the same
server, and the terminal server clients had their own server. I have also
had multiple terminal server clients on the same server as the back end
without any problems.

In your case, I'd set up perfmon.exe to monitor the terminal server since,
that is probably the cause of your problem.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.mvps.org/access
http://www.accessmvp.com



.