[AccessD] Terminal Server and Access XP

Right... you give them the normal shortcut to the FE in the Terminal
Services window and Terminal Services will do the rest.

It will work just as though you had one FE on a regular windows network. So
if your app requires separate front ends for each user as most of mine do,
you will have to set up separate FEs for each user on Terminal services.

It is an awesome product.  Performance is outstanding and you can shadow the
user which makes support and training a breeze.

-----Original Message-----
From: accessd-bounces at databaseadvisors.com
[mailto:accessd-bounces at databaseadvisors.com]On Behalf Of Steven W.
Erbach
Sent: Thursday, November 20, 2003 7:31 AM
To: Access Developers discussion and problem solving
Subject: RE: [AccessD] Terminal Server and Access XP


Greggs,

Thanks for the clarification. What floors me is that there is *anything*
that requires a DOS command prompt in Windows these days.

Since I'm a rookie with Terminal Services let me see if I've got this right.
I can install one copy of Access XP Runtime and one copy of the FE for my
Access application on the Terminal Services server. The BE is also installed
there. Then anybody that is a user of the Terminal Server loads a copy of
Access XP Runtime and my application into a "separate" memory space on the
server and just the screens are sent down the wire to the user's
workstation/terminal. All of the normal Access processing of queries and
reports and such is done on the Terminal Server for each and every user of
the Access application.

Have I got that right?

Regards,

Steve Erbach
Scientific Marketing
Neenah, WI

Disclaimer: No tree was killed in the transmission of this message. However,
several coulombs of electrons were temporarily inconvenienced.

_______________________________________________
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com