Microsoft Access 2003 problem: cannot run reports when connected to networked printers
June 21, 2006
11:13 pm
Vasken
Musings
Tags: , Access, Access 2003, bug, connection, database, local, Microsoft, networked printer, printer driver, problem, queries, report, reports
There is a bug/weakness in Microsoft Access 2003 that I have come across recently, and it’s an insidious one. Basically, the problem manifests itself as an inability to run user-generated reports from a database. Everything else works fine–the connection to the database itself is sound, the user can run queries, view data, and do everything else imaginable except run a report.
The solution is maddeningly simple once you figure it out, but it took me quite a while to get there, so maybe I can spare some other people the time: Access runs reports via the printer driver of the default printer, and for some reason, if that printer is a networked printer, Access can’t generate the report. Queries, as a simple data-retrieval operation, do not require the driver–it’s only used in the context of the user-defined, formatted view offered by Access reports. This seems remarkably stupid, since a database application needs to run in an enterprise environment, and that implies networked laser printers.
The workaround, of course, is to install the printer locally. To do this, choose local, rather than networked at the first add printer splash screen. Then, add a local port as the name of the printer on your network, i.e. \\printers\treekiller, or through the IP, and voila, you’re connected in a way that Access 2003 understands. Seems a bit foolish, doesn’t it?
Duane Durocher :
Date: January 16, 2008 @ 9:32 am
I just want to thank you for this post - This is exactly what happend to me but I did not know at all where to go. Your post is very much appreciated. Thanks again.
parker :
Date: January 23, 2008 @ 4:17 pm
Seconded: I would have never figured this out. Thanks so much for posting this.
Robert :
Date: June 19, 2008 @ 1:12 pm
Just wanted to make you aware of another issue that I ran into. If you have a banner page enabled within your print properties. You will run into the same issue as above. Thanks for this post as it helped me trace my this problem.
Dave G :
Date: July 23, 2008 @ 1:32 pm
Super. Thought i’d just killed my computer and was going to have to get on the blower to the IT department tomorrow to get access reinstalled, but you’ve just saved me the bother.