Windows Terminal Services

[Greg]

I just demonstrated our MS Access XP (ADP) software that connects to SQL
Server 2005 software the other day to a potential customer.

They happen to run a Macintosh environment and then run Windows Terminal
Servcies so they can run Windows applications on these machines.

We had a recent customer who attempted to install our software to run on
Terminal Services and had no success. Apparently, what happened was the first
client would load just fine, but then the second client would return an error
that it could not find the server. They were not able to troubhshoot the
problem and since I do not have Terminal Services in my office I have little
to no idea how it works.

Anyway, this potential client asked me if it would run on Terminal Services.
One would think it should, but in our experience so far it does not.

Is it possible for a MS Access ADP application connecting to SQL Server 2005
to run with multiple logins via Windows Terminal Services?

Thanks,
Greg

 

[Sylvain Lafontaine]

You shouldn't have any particular problem running ADP on TS.

In your case, the cause is likely because all users are sharing the same
copy of the ADP - instead of having their own copy - and that you are
dynamically changing the connection (using .OpenConnection) and/or are
making dynamic changes to records source and row source with VBA code.

Make sure that each user has his/her own private copy of the ADP file and
you should be OK.

 

[David W. Fenton]

Is it possible for a MS Access ADP application connecting to SQL
Server 2005 to run with multiple logins via Windows Terminal
Services?

I don't do ADPs, but I have plenty of apps running out there with
MDB front ends running against SQL Server and Jet, and they work
just fine on Terminal Server. I can't see why an ADP would be any
different.

One key issue may be that with MDBs each Terminal Server user needs
her own copy (just as they would have their own front ends if
running from a workstation). Given that the problem occurred when a
second user attempted to log run the app, this suggests that the
problem was with trying to share the ADP.

But I'm just guessing there.