View Single Post
  #8  
Old May 3rd, 2010, 10:32 PM posted to microsoft.public.access
Arvin Meyer [MVP][_2_]
external usenet poster
 
Posts: 2,310
Default Access database SQL split and Terminal Services

Make sure that the PC is running the front-end from a workstation, not the
server. Each of the Terminal services clients need their own copy of the
front-end. I usually do this by creating a folder for each thin client user
and putting a copy of the front-end in it.
--
Arvin Meyer, MCP, MVP
http://www.datastrat.com
http://www.accessmvp.com
http://www.mvps.org/access


"kaylee" gybrvuh28185 wrote in message
...
fkfneerereegjnrnerneeeyr
"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.

Thank you,