TO PRINTER PROMPT PREVIEW causes blue screen

[LorenC]

I have almost 200 customers and two of them have the same problem.
When they go to print a report or preview a report their computer blue screens.
They both have different printers. One made his computer, the other bought a laptop.

The only common items is they both have windows Me and the AMD chip. I use Me with no problem. But I'm sure other customes must have the AMD chip also and no reported problem.

The one customer says if he tries to print the report 3 or 4 times, it will print the report but has to go thru 2 or 3 blue screens to do it.
Yet he can use Microsoft Word and print without a problem!
Why the difference?

The one customer has updated his printer driver and checked for update on Me but still has the problem.
I can not find an answer to this.
Has anyone run across this problem before?

 

[Mike Gagnon]

LorenC

Although the solution was originally intended for HP printers, you may consider trying the solution proposed in FAQ184-2265. Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.

 

[LorenC]

Thanks Mike,
This is the first of any code I've received to help with the problem.
But how do I know what they have on there system if I hard code with MSVCRT, MSCVRT10 OR MSCVRT20

Would it be wise to copy my copy of say, MSCVRT20 into their windows system so they have it?
Then the hard code might work?
Just not sure on this....

 

[rgbean]

Both MS KB articles that reference this problem show MSCVRT20 -

http://support.microsoft.com/default.aspx?scid=kb;en-us;253356

- "PRB: "API Call Caused an Exception" Error Message with Third-Party Print Drivers" and

http://support.microsoft.com/default.aspx?scid=kb;en-us;183522

- "FIX: Divide by Zero Creates Err with Third-Party Print Drivers".

Note: It's not a good idea to copy around system DLL's. The MS DLL Database shows a number of different versions of these DLL's (

http://support.microsoft.com/default.aspx?scid=/servicedesks/fileversion/dllinfo.asp&fp=1).

If you've used the Setup Wizard to install your application, I believe it will install the proper one if it's not already there.

Rick

 

[Mike Gagnon]

LorenC

Although I have used MSVCRT (under Win'95 I believe), I would go with Rick's (Welcome back Rick) suggestion and use MSVCRT20.dll (The registered type). Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.

 

[rgbean]

Thanks Mike,
I just took a much needed vacation, but I'm back now and ready to go!

Rick

 

[rianeiromiron]

Just in case this helps you:

I ran into the same problem specially when using LEXMARK printers or XEROX printers. However, the solution was not in updating drivers but rather install service packs for VFP, I was using VFP 6 those days, then I recompiled (I use only EXEs) and the problem was solved.

Hope that helps

Rianeiro

 

[LorenC]

Thanks Rianeiro,
I'm using VFP7 with sp1.

I'm using Mike Gagnon's idea with the msvcrt's.
I made a routine to search for all the msvcrt's on the customers machine and picking msvcrt20.dll if it's there.

Also I made a dialog for the customer to change to a different one on his machine in case the above one doesn't work. He can try them all till he finds one that works, if this works at all.

I have msvcrt.dll, msvcrt10.dll, msvcrt20.dll and msvcrt40.dll on my machine using windows Me.

By the way, Thanks Mike Gagnon for the help.
Loren

 

[Mike Gagnon]

Loren

By the way, Thanks Mike Gagnon for the help.

You are welcome.
Mike Gagnon

If you want to get the best response to a question, please check out FAQ184-2483 first.