>Have you seen any of the threads regarding the _FPRESET() from the KB about lockups due to using HP printer drivers. You need to declare the _fpreset and then call the _fpreset() after printing a report or using the GETPRINTER() or SET PRINTER TO commands. Apparantly the HP drivers set the Floating Point divide by zero to software instead of hardware. I don't know that that is still the problem. Also another major one is that you should distribute the latest OLEAUT32.DLL and the other updated files from the SP2 for VS 6.0.
Rich,
Excuse me for nosing in. A number of members have suggested avoiding HP drivers as a way of preventing strange printing results, but this is the first time I have seen a reference to _FPRESET() as a cure.
Every once in a while I experience a partial lock where menu drops cease to function (not the main bar, just the drops) after previewing or printing a report. I wonder if _FPRESET() would not be a solution?
Is the KB you refer to here on the UT or the MS KB?
regards,
Jim Edgar
Jurix Data Corporation
jmedgar@yahoo.comNo trees were destroyed in sending this message. However, a large number of electrons were diverted from their ordinary activities and terribly inconvenienced.