>Hi Rich,
>>
>>I spoke to our NT administrator, and according to him...: MS does *not* supply printer drivers; they just publish a
>>spec that manufacturers (such as HP) follow and then write the driver for. He is going to try the tact of re-establishing
>>(deleting and redefining) our NT print server queue and see if that does anything. Short of that, he really has no clue.
>
>I don't know what you're using for a workstation (we use Novell and Win98), however, if I open the printers folder, bring up the property sheet for our HP Laser Jet 4L, then try to change the driver, there's a list box with over 100 HP drivers that comes with Win98 SE. I don't know about NT workstation, but you can tell your administrator he's dead wrong about MS not supplying drivers for hardware in Windows.
>
>>He thinks that it *IS* a VFP problem, since it doesn't happen with other apps such as Excel or Word (yet he cannot
>>point to a 1,400 page Word document that prints daily without hanging <s> )....
>
>I think he's wrong again. Prior to SP3, if you had a report that inadvertantly did a division by zero, and tried to send the report to an HP printer VFP ended up GPFing. Why? Because the driver re-set the state of the FPU (normally the hardware is responsible for catching certain errors and the HP driver made the software responsible). VFP's problem? Nope, because the specs say not that the driver shouldn't. Further, something like Excel wouldn't have this problem, since Excel doesn't calculate it's values during the print process. Further, I know that this occurs under other languages. I've heard that MS tried to convince HP to mend their ways, and HP refused. Anyway, the good thing was that SP3 fixed the problem.
>
>My money's still on it being a driver issue. Get an MS driver.



This always worked for us:

Try to downgrade the printer to something like laserjet III. It worked like a dream.

Good luck


Eylon