Access crashes after second print and event ID 1000 logged.

[Guest]

XP Pro SP2 with access has been giving us some unusual errors. When we
attempt to print from our database, it will print right the first time. If
you hit the print button again, to print a second report access crashes. The
event viewer log says:

"Faulting application msaccess.exe, version 8.0.0.5903, faulting module
msaccess.exe, version 8.0.0.5903, fault address 0x000a24dd."

I am unsure to start with this problem. Any suggestions would be
appreciated. Thank you!

 

[Tony Toews [MVP]]

XP Pro SP2 with access has been giving us some unusual errors. When we
attempt to print from our database, it will print right the first time. If
you hit the print button again, to print a second report access crashes. The
event viewer log says:

"Faulting application msaccess.exe, version 8.0.0.5903, faulting module
msaccess.exe, version 8.0.0.5903, fault address 0x000a24dd."

Do please send those error reports to Microsoft as, while they don't
like getting them, they do pay a lot of attention to them and fix them
as promptly as possible.

What happens if you try printing to another printer? If you don't
have another printer try installed PDF Creator from sourceforge.net.

Have you tried locating a newer printer driver for that printer? If
you have the latest printer driver see if there's a recent Windows
Certified printer driver. Sometimes the newest printer drivers can
contain bugs.

Ton
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/

 

[Guest]

Hey Tony, thanks for the quick response.

We will start sending those reports to microsoft el pronto.

What happens if you try printing to another printer? If you don't
have another printer try installed PDF Creator from sourceforge.net.

When the error occurs, they are using a print preview button created back
ages ago, that I believe probably had a printer tied to it. Since we changed
to the new server, (old network was NT and 98) several of these buttons when
used request that you choose a default printer as they don’t recognize the
old printer setting. Once they get this message they click the print button
again and magically it recognizes their default printer. I would venture to
say that the printer name having changed somewhat is part of this problem,
however that doesn’t explain why it locks up and kicks you out. Typically it
is only happening on a select few of these buttons. Since I’m not an access
visual basic code expert, I’m not quite sure how to go about changing.

Have you tried locating a newer printer driver for that printer? If
you have the latest printer driver see if there's a recent Windows
Certified printer driver. Sometimes the newest printer drivers can
contain bugs.

At one point we were using PCL drivers, but had so many errors, a printer
tech switched it over to PostScript for us. The printers themselves sit on
2003 server and we access them via the network \\server\printersharename etc.
Do you think this sounds more like a printer driver problem or an access
problem?

Thanks again!

 

[Tony Toews [MVP]]

When the error occurs, they are using a print preview button created back
ages ago, that I believe probably had a printer tied to it. Since we changed
to the new server, (old network was NT and 98) several of these buttons when
used request that you choose a default printer as they don’t recognize the
old printer setting. Once they get this message they click the print button
again and magically it recognizes their default printer. I would venture to
say that the printer name having changed somewhat is part of this problem,
however that doesn’t explain why it locks up and kicks you out. Typically it
is only happening on a select few of these buttons. Since I’m not an access
visual basic code expert, I’m not quite sure how to go about changing.

I'm thinking that those few reports might be tied to a specific, now
non existent printer. While in the report design view click on Filesection. Is it set to Default Printer or a specific printer.

At one point we were using PCL drivers, but had so many errors, a printer
tech switched it over to PostScript for us. The printers themselves sit on
2003 server and we access them via the network \\server\printersharename etc.
Do you think this sounds more like a printer driver problem or an access
problem?

<shrug> Hard to tell yet.

Tony
--
Tony Toews, Microsoft Access MVP
Please respond only in the newsgroups so that others can
read the entire thread of messages.
Microsoft Access Links, Hints, Tips & Accounting Systems at
http://www.granite.ab.ca/accsmstr.htm
Tony's Microsoft Access Blog - http://msmvps.com/blogs/access/