Thanks,
I'll try this.


>This is a know problem in VFP5 when using non-Microsoft printer drivers - especially HP. The HP driver tells the processors floating point processor not to handle divide by zero errors. The driver handles the error when it comes back from the fp processor. Unfortunately, the printer driver does not turn the error handling back on when it is done.
>
>If an error occurs later, it is passed back to VFP who is not ready to handle it (assuming it will be dealt with in hardware).
>
>The good news is that there is a work around. In your main program declare a function to reset the floating point processor to default state and then call that function a lot - particularly after any print operation. Specifically:
>
>declare _fpreset in msvcrt.dll
>
>= _fpreset()
>report form something to print
>= _fpreset()
>
>BTW, the printer driver does a lot of dividing to calculate spacing and placement of characters. In addition, the printer driver is called for certain screen operations too.
>
>I still use VFP 5.0, but the best fix seems to be to upgrade to VFP 6.0 and apply service packs.