Microsoft Access 2003 problem: cannot run reports when connected to networked printers
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?
Comments
Duane Durocher (Jan 16, 2008)
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 (Jan 23, 2008)
Seconded: I would have never figured this out. Thanks so much for posting this.
Robert (Jun 19, 2008)
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 (Jul 23, 2008)
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.
Steve (Feb 18, 2009)
Alas, the problem is not just that the printer is on a network. I can solve the problem by switching to a DIFFERENT printer on the same network.
Vasken (Feb 18, 2009)
@Steve,
That depends. Is the other networked printer installed as I recommend above, whereas the one that does not work is installed as a ‘pure’ networked printer? I suspect that’s the reason you’re having intermittent success between network printers.
Access 2003 (Apr 22, 2009)
Thanks for the tip, finding this saved me a lot of trial-an-error attempts.
Carey (Aug 17, 2009)
THANK YOU for posting this! I never would have thought to check the printer.
Felicity (Dec 15, 2009)
Thank you VERY much for posting this. This information was dead on the money, and saved me probably several days worth of frustration. I had an old Access (2000) application still running in Access 2003/Windows XP. I would never have thought to check the printer, because it is irrational. Your solution worked exactly as you described; and that too is irrational. Whatever. THANK YOU!!