I'll add a little to Christof's post about running _fpreset() in that you must run it before processing any "Set Date" command when using HP printer drivers. No idea why but it is the only way to make the drivers play properly and HP have never fixed this after 18 years to my knowledge.
What makes it more annoying is that the errors occur randomly which made tracking them down even more difficult than it should have done until I discovered _fpreset()
Dave
-----Original Message----- From: ProFox [mailto:profox-bounces@leafe.com] On Behalf Of Wollenhaupt, Christof Sent: 12 April 2017 10:59 To: profox@leafe.com Subject: Re: VFP EXE and RDS random crashes
To that point--would copying the FRX/FRT locally and running from there be a better option to avoid that?
It would depend on which file is causing the problem... It certainly would be worth a try. If the EXE or any of the REPORT*.APP files is on the network it also would help to copy those to a local drive. Same is true for any DLL or OCX you use.
Another issue that causes crashes mostly when printing, but usually wouldn't result in a C6 exception, is the floating point problem. 15 years ago HP printers where notoriously famous for changing the exception handling for the floating point unit so that a division by zero caused a crash instead of returning NaN (not a number).
To work around this, we have
DECLARE _fpreset in MSVCR71.DLL _fpreset()
everywhere in our program where we access a printer driver. So before and after printing a report, selecting a printer, listing printers, etc.
-- Christof
--- StripMime Report -- processed MIME parts --- multipart/alternative text/plain (text body -- kept) text/html ---
[excessive quoting removed by server]