Default Printer Changes

[John Ritter]

I have created several data bases that are used throughout my company. This
has caused several issues when the default printer is different than my
default printer. Example. I run the report on my desktop and the reports
print out on my default printer. My default printer breaks down. I change
my default printer and the database crashes. I change my default printer
back and the same data base runs just fine, but no print out. Additionally,
when I try to open the report in design view while the default printer is not
on the original printer the data base crashes.

Is there any solutions to this issue or must all the reports be sent to a
specific printer?

 

[Allen Browne]

That should not be happening, John. If you leave the report assigned to the
default printer, it should work with other printers to, unless you used some
features that are not available on other printers (e.g. if you set up the
report for A3 paper, but others only have A4 size.)

What version of Access? And what Service Pack?
(Help | About should show the SP.)

Have you turned off Name AutoCorrect:
http://allenbrowne.com/bug-03.html

Compact the database:
Tools | Database Utilities | Compact/Repair
or in Access 2007:
Office Button | Manage | Compact/Repair

Does it crash with one specific printer only?
If so, that could indicate a faulty printer driver (even if the printer
works on other contexts.)

Access 2003 is particularly sensitive to network printers that are not
installed quite right, or where you don't have adequate rights. You might
examine the Printers collection to see what it has to say.

In general, the default printer is the way to go, and works fine across a
wide range of computers and their printers.

 

[Mike]

I'm having a similar problem. We have an Access database (used as a front end
to a SQL database) with 400 reports. Recently, when opening reports in design
view, I get the message that the report was not formatted on a certain
printer and would I like to use the default printer. The first printer is a
non existent former Network printer and the reports take forever to open in
design view. (We made the network change in printers quite sometime ago, so I
don't know why this came up suddenly). What's more is that in production when
a user prints a report, the application first opens the report in design view
to add a tag. So, we are experiencing serious performance problems for our
users. Any ideas on how to programmatically modify the printer that the
report was formatted with. I really don't want to open each of the reports
and click yes to the prompt for changin printers. And then of course, what
happens when we get a new printer? As I mentioned, this started happening for
no obvious reason a couple of weeks ago. Any help or suggestions would be
appreciated.