You should be able to map the default local printer so that Access (running
on the Citrix server) uses the mapped printer as the default printer for the
user.
In fact, this is done automatically by Citrix server and you have to
instruct Citrix not to map if you don't want local printer mapping. The
only requirement is that the printer driver MUST be available on the host
server.
One problem is that the mapping takes a fair bit of time if you use
non-laser printers. The problem is that most (if not all) inkjet printers
are Windows printers, i.e. relying on the host CPU to do all the printing
processing and the mapping process takes a fair bit of time, especially on a
slow link, since the host has to communicate with the printer to get all
printer settings & conditions. For a laser printers, the printer has its
own processing CPU and the host CPU does not need to know a lot of details
re the printer and therefore, the mapping is a lot quicker.
I have remote users (3000 km away) using Access via Citrix and once the
mapping is done, users can print without any problems.
--
HTH
Van T. Dinh
MVP (Access)
"tom" <to*@nuws.com> wrote in message
news:c1**************************@posting.google.c om...
We host our Access 2002 application on Citrix, and printing is
definitely a headache area. One solution we have when users are having
printing trouble is to utilize Access's ability to save a report in
Snapshot format onto the user's local machine. That way they can open
it locally and print it just fine. The snapshot files tend to be quite
teeny, so they transfer in a snap. Not an ideal solution, but
workable.
-TD
