View Single Post
  #2  
Old May 22nd, 2004, 07:55 PM
Steve Schapel
external usenet poster
 
Posts: n/a
Default Problem with printing reports

Endus,

Your comment "someone else in his area switching it to specific printer
and saving it" makes me wonder whether you have multiple users accessing
the same application file. If this is the case, I can't suggest a
specific explanation for the printing problem, but this configuration is
"asking for trouble". Consider placing the core data tables in a
separate MDB file on the server, and linking to this backend from
individual application frontend files installed separately on each
workstation. Also consider saving these applications as MDE format, in
which case users will not be able to change the settings. I apologise
if I have misinterpreted your situation. Please post back if you need
further help with this.

--
Steve Schapel, Microsoft Access MVP


endus wrote:
Hi,

I have this user who is having trouble with the print options for
reports for certain reports. The person sets the report to print to
the default printer. This is the desired and necessary setting since
people are accessing the database from multiple locations and it is
important for security reasons for reports from other people not to be
spitting out of the printer in his area without his knowledge. He
sets the printer to default printer and it's fine for a while.

Eventually the printer switches to specific printer, with the printer
in his area being specified. This happens to users in another
location who are unlikely to know the name of his printer, much less
have a reason to print to it.

I have searched google and Microsoft's site and have not seen a single
mention of a problem of this nature. I haven't been able to duplicate
the problem on my own test machines, but I also haven't had an
opportunity to try it with the DB that is exhibiting this behavior
yet.

It occourred to me on Friday that this may be a PEBKAC issue with
someone else in his area switching it to specific printer and saving
it. I'm not sure if there is even anyone else in his area accessing
this DB though, and I am pretty sure that he would have mentioned the
problem to anyone working on this DB. I am going to check on this
possibility Monday, but I was wondering if anyone had seen anything
like this before.

Thanks!
~ endus ~~ at ~ endus ~ dot ~~ com ~

But what the hell. It is a good & healthy thing
to have a fine fat steak & a bottle of good Kentucky
bourbon & order cameras from Hong Kong & generally
feel rich. - Hunter S. Thompson