Access runtime error 3011 on docmd.openreport

[enough2Bdangerous]

access runtime error 3011 on docmd.openreport
--------------------------------------------------------------------------------

Access database (file format 2002-2003) generates reports with docmd.openreport but returns 3011 runtime error related to the printer. Switching Windows default printer is a work around but need to find out the cause. Help Desk updated printer driver on server and no runtime error for two months but we are receiving it again on three computers.

I think this might be specific to the actual mdb file and what occurs with references, dll's, etc. rather than the printers themselves. Windows default printer works for Outlook, Word, Notepad, etc. so this is specific to the print preview portion of Access reports and it has happened in print preview of Excel.

Received error recently, switched printer to work, switched back to problem printer without help desk and worked fine......

Could be related to XP conversion too, not sure...but need help.

[Cyberdyne]

We might want to move this thread to the access forum, would you like me to?

It sounds to me like a problem with your access code not the printers or their drivers, although the excel print preview made me think twice. What happens when you try and print preview a file in excel? Is it the same error?

[enough2Bdangerous]

We might want to move this thread to the access forum, would you like me to?



It sounds to me like a problem with your access code not the printers or their drivers, although the excel print preview made me think twice. What happens when you try and print preview a file in excel? Is it the same error?

I really appreciate the reply....
I was advised by the Access moderator to post in Windows. The Help Desk here seems to think it is related to the program within Access specifically, not Access and not the printers and/or drivers.

I'm not sure if the program is corrupt or that it was converted from 97 to current version using a newer version of Access than we are actually running.

Didn't receive the same error but the page setup response time in Excel is delayed drastically. For example, when you change the margins, what normally would take a less than a seconds drags on for about 15 minutes.

[Cyberdyne]

Seems to me like its using a lot of processing power from your CPU, can you contact the people that made the program within access and see if they have updates?