>>>>The problem is:
>>>>
>>>>Facts:
>>>>
>>>>VFP 5.0a
>>>>Win 98
>>>>Printing to the HP6P Enhanced or later HP Printer driver (regardless of specific printer - the 6p enhanced was the first where the problem showed up.)
>>>>
>>>>Usually the 98 machine is mapped to the printer through Novell File & Print shareing Service - as opposed to the Microsoft service. This seems to agrivate the situation, but is not required for it to happen.
>>>>
>>>>Problem:
>>>>Once the system has printed, it will get an Exception error. The simplest reproducable example was a program that did this:
>>>>
>>>>type c:\autoexec.bat to print
>>>>select * from tablea, tableb where tablea.field = tableb.field
>>>>
>>>>Where the mapping field was an integer, and one of the tables had stars (****) in the field.
>>>>
>>>>Note: The problem often occured on other commands in different parts of the system, such as setting an Enabled=.T., a DODEFAUL() - didn't really matter. Once VFP printed to that printer, the damage was done, and it would soon crash.
>>>>
>>>>Again, this does not happen with any printer prior to the 6p.
>>>>
>>>>Any ideas?
>>>
>>>
>>>Yup. there are known problems with the HP drivers and several applications...not just VFP.
>>
>>
>>Is HP aware of the problems? Are they working on it? Any chance of a solution? It's kind of tough telling my customers "Gee, I can't do anything, sorry..."
>>
>>Joe G.
>
>
>You might try the latest drivers. However, I found that PCL 6 has problems. We have an HP 4000 and are using the PCL 5 driver.

We are using the 2/28/98 drivers - the latest they have. At any rate, We found a solution & work-around on the below MSFT Knowledget Base article. It appears the printer drivers are goofing up the math coprocessor:

Microsoft's solution:
http://support.microsoft.com/support/kb/articles/q183/5/22.asp