I cannot remember if I replied to this before but I notice it is really old - forgive me if I did!

We basically solved it by having users print out through the PostScript (PS) printer driver. Since the problem was most evident on our latest printers (HP 4050 and 4100) and since they contain the ability to print PS files without buying an add-in cartridge etc, it was easy enough to have the users print through this driver instead. I don't know if the other tech guy set this up as their default printer so that they print everything through PS but if not, the users must know enough when printing a report from the database to use the PS driver.

Hope this helps. Not a real solution to the regular printer driver problem but we spent probably 50 (yes a "5" and a "0") of billed time to get to that point as MSFT and HP were no help!

Albert

>Dear Albert,
>
>You were discussing the HP - VFP printer battle. We have an application that on some computers, at some locations GPFs unless the Microsoft built HP printers are installed. Of course, MSFT does not update their print drivers for HP's latest printers. So, we end up telling the user "Oops sorry you need to install an HP Laserjet 4 driver and oh by the way if that does work try the HP Laserjet 3". Ouch!
>
>I called MSFT paid support and they offered debugging information but little else besides the usually try the earlier MSFT drivers.
>
>So I was wondering if you had any new info on this issue.
>
>By the way, I read FPW2.x DOS had a SET FOXPROX=-saveregs command which told Foxpro not to mess with register settings. I have not found anything similar in VFP.
>
>Regards,
>
>Jim Smith