MS Access and Terminal Services - any issues?

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

Hi all,

Does anybody know of any issues that may arise when using MS Access databases on Terminal Services? We have an application that works on Windows 98-Windows XP but have never had the requirement to use and test it on Terminal Services. It's the usual backend on server with frontend on the client, and is integrated with MS Word and MS Excel.

My main concerns are how local tables are dealt with and also common problems that I may have to look forward to...

Many thanks in advance,

Stuart
 
Stuart said:
Hi all,

Does anybody know of any issues that may arise when using MS Access
Click to expand...
databases on Terminal Services? We have an application that works on
Windows 98-Windows XP but have never had the requirement to use and test it
on Terminal Services. It's the usual backend on server with frontend on the
client, and is integrated with MS Word and MS Excel.
My main concerns are how local tables are dealt with and also common
Click to expand...
problems that I may have to look forward to...
Many thanks in advance,
Click to expand...

In my (and others) opinion, the use of Terminal Server does NOT negate the
strong recommendation that each user have their own individual copy of the
front end. Of course when you do that then the issues you describe become
non-issues.

Our system uses a published app that is actually a BAT file that creates a
copy of the Access file in the user's home folder and then opens it.
Updates are then issued exactly the same as they are for users not running
through Terminal Server.

The big "issues" I have to deal with are when the Access app needs to print
or send Emails. Printing through TS has issues with any application and
Emails require that each user have an Outlook profile created on the
server.
 
Back
Top