We did fix the Divide By Zero issue in VFP6 as indicated in the KB, however, I am wondering if there may still be unrelated FP issues associated with these printer drivers (which we will of course investigate this).

So, if you are experiencing similar problems, you may still want to follow the instructions to call _FPRESET() after any command which could invoke the printer driver. Here are just some examples:

REPORT FORM
GETPRINTER()
SYS(1037)
SET PRINTER TO NAME
Clicking the "Print One Copy" button on the FoxPro toolbar.

I'm not sure about placing this call in BeforeOpenTables method (I never tried this), however, you could always be ultra safe and call _FPRESET() both before and after printing reports.

Randy

>>Have you guys checked out KB article KBQ183522 which is on our support site (http://support.microsoft.com/support/).
>>
>>It discusses the floating point issues with the HP drivers and how you can workaround these problems by calling _FPRESET() after printing.
>>
>Hi Randy,
>
>Having some familiarity with the KB article brings up the following question. In the article it says: "In the case of a report, placing "=_fpreset()", without the quotes, in the BeforeOpenTables method of the report prevents the error." However, from what you're saying this is wrong. Or am I missing something?