Re: Why can't I print reports on Citrix network?

Printer set up is a bit obscure on Citrix. When properly set
up, each user prints at his local printer, even though he is
running on a server somewhere else. To do this, his printer
driver is installed on the server each time he logs in. So
you have to get the printer installation correct, as well as
getting the profile correct.

Like in all network installations, Access is the first program
to fail, and fails the worst, if there is any kind of problem.

Your report that only Access fails, and Access only fails
for one user, is not unusual. There is no point testing from
your profile, the problem is in the user permissions and
profile.

Not normally anything you can do to Access to fix
the problem unless you have reports set to print to a particular
printer driver - that can cause problems..

(david)


"Jeff Stroope" <JeffStroope@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:CA8E0800-CFDE-439D-82B8-E1FBD08B08D0@xxxxxxxxxxxxxxxx
Hi,

I'm trying to help a user who is not able to print reports in an Access
database. We aare on a Citrix network. The user is a thin client. The
database is on a network file server. When he tries to open a report,
nothing happens. The queries and tables in the database all run fine and
display properly. I think the reason the reports won't even preview is
because the database doesn't "see" a printer, but maybe I'm wrong.
Anyway,
the user is able to print Word documents, but not Access reports. I went
back to my computer (fat client), logged onto Citrix on the same server
that
the user is on and I have no trouble previewing or printing the reports
from
the database. Does anyone know what's going on here? Is this an Access
problem or a networking problem?
--
Thanks,

Jeff


.

Relevant Pages

  • Re: SYSTEMS ENGINEER/ VAX-VMS/ CAREER POSITION
    ... System Administration and database admin from NIIT, ... salary details and generate reports and enclosures,and calculates ... Responsibilities: ... Write New programs from user requirements, Programming Changes ...
    (comp.os.vms)
  • Re: Advice needed for a growing Access 2000 project
    ... However, it turned out that quite a few of those were "leftovers" from previous releases, no longer accessible from anywhere but the database window, and, thus, no longer used. ... But that certainly isn't the _norm_ -- without any 'heroic' measures, there are routine reports of split Access DBs ... Finally, in my opinion, for "Windows apps", that is, individual-user applications, modest-sized multiuser applications, and client-server applications of any size, Dot Net does NOT "help along" any of these issues. ... The post I reference was in reference its self to the MS Access Help file under "Microsoft Access database general specifications" ...
    (comp.databases.ms-access)
  • Re: running report cause fatal error- on Win98, not XP
    ... It is actually not that difficult to crash JET with complex queries, ... another query. ... only the more complex reports cause the crash- the others do ... Then compact the database: ...
    (microsoft.public.access.reports)
  • Re: running report cause fatal error- on Win98, not XP
    ... another query. ... only the more complex reports cause the crash- the others do ... Then compact the database: ... Still in the code window, choose Compile from the Debug menu. ...
    (microsoft.public.access.reports)
  • Re: WHY
    ... As most database processing doesn't take place on Windows systems, ... >spreadsheet and copy if every month.. ... prejudiced to learn that reports aren't the only thing spreadsheets can do. ... since the number of periods over which loan payments could be made is ...
    (microsoft.public.excel)