MikeAngelastro
Registered User.
- Local time
- Today, 08:12
- Joined
- Mar 3, 2000
- Messages
- 254
Hi,
We have just migrated our Access 2002 accounting application to Windows 2000 Terminal Services. We have about 12 clients connected and using the program. It seems to be working OK except for a few nasty little glitches - unexpected errors.
Everyone is using the same front end. We have enough memory on the server to handle everyone being connected at the same time. It works pretty fast.
When a client gets an error, we reset him/her. But the error is likely to return unless the user either restarts or actually turns off/on their machine. This suggests that the problems are with the client machines and not Terminal Services; but I'm not sure.
Does anyone have any advice on how we can configure our TS setup to minimize or eliminate the possibility of problems. Is there a good book or article that would be helpful.
Thanks,
Mike
We have just migrated our Access 2002 accounting application to Windows 2000 Terminal Services. We have about 12 clients connected and using the program. It seems to be working OK except for a few nasty little glitches - unexpected errors.
Everyone is using the same front end. We have enough memory on the server to handle everyone being connected at the same time. It works pretty fast.
When a client gets an error, we reset him/her. But the error is likely to return unless the user either restarts or actually turns off/on their machine. This suggests that the problems are with the client machines and not Terminal Services; but I'm not sure.
Does anyone have any advice on how we can configure our TS setup to minimize or eliminate the possibility of problems. Is there a good book or article that would be helpful.
Thanks,
Mike
