terminal server printing

  • Thread starter Thread starter Rob Schottman
  • Start date Start date
R

Rob Schottman

I have recently converted a fairly large company with many
offices in many towns from an Access 97 database up to an
Access 2000 database that runs on a Windows 2000 server
Terminal Services. The users connect via VPNs using the
public internet. Everything is working well except for
one strange anomaly. With many users all connected and
in the database at the same time - the default printer
that each user sees whenever they go to print a form or a
report seems to be the printer that the last user to print
used. For instance, if user A printed a report to
his/her Terminal Services auto-created remote printer
sitting right next to them, - then, 2 minutes later - the
very next user to print anything from the database is user
B - who, sees users A's auto-created printer as the
default printer for the report instead of his own auto-
created printer. So, user B changes the printer to
his/her own printer. Then, when user A goes to print
again - he/she sees user B's printer as the default.
Add about 50 users to this senario and it is getting
frustrating for the users who all are used to the way it
was before when their own default printer is all the ever
showed up. Seems like now matter who prints - they see
the last printer used from anywhere in the database as
their default printer instead of their own.

HELP!!!!
 
Rob:

The rules with Access dbs operating successfully in a multi-user environment
hold true whether that environment is on desktops or in a Terminal Server
scenario. The only way to successfully isolate one user's operations with
forms/reports etc within the database is to split the db into front end and
back end and give each user their own front end application to access,
linked to the back end data.

More maintenance? Yes; Better User Experience and Performance? By Far.
 
Back
Top