>>>>>>>>>>>>
>DECLARE _fpreset in MSVCRT && only needed once
>=_fpreset()
>
>This resets the state of the FPU and MMX register - some printer drivers do not clean up after themselves, leaving the FPU in an unstable state. This clears the FPU. You should call this after every printer operation.
>
>VFP SP6 addresses this itself.
>>>>>>>>>>>>>
>
>A question Ed, I'm also having a silimar problem but using the report within Foxpro not PDF. Would this solution apply also. (BTW 4 machine are running win98, 4 have the same exe and only 2 crash the other 2 are fine.)

>>If the problem is related to the print driver not resetting the floating point processor, yes, otherwise, no.

It's seems to be related to the printer driver since 2 of the 4 machine are working fine. I'll try hyour solution. I just assumed Foxpro would have the solution to everything and I would'nt have to go to API.