Gregory, I tried your suggestion to set resource off, delete the foxuser file etc. but .. we still get these fatal errors. Anyway, thanks for the suggestion. Does anyone else have any ideas? Denis


>I am going nuts trying to find out what is causing fatal errors in my app. on some PCs but not others. They started after upgrading from VFP6 to 7. No changes to my code - just the upgrade. Is there a way to send this to MS? A typical error report below. Line 580 is "Read events". Denis
>
>Fatal error: Exception code=C0000005 @ 11/04/2003 04:34:13 PM. Error log file: C:\BRAHMS5\VFP7Rerr.log
>> Called from - setbrop line 580 {C:\shared\prg\setbrop.prg setbrop.fxp}
>> Called from - rde line 109 {C:\BRAHMS5\prg\rdelib.prg rdelib.fxp}
>> Called from - menuexecute line 692 {C:\shared\prg\menus.prg menus.fxp}
>> Called from - runmenu line 36 {C:\shared\prg\menus.prg menus.fxp}
>> Called from - brahms5 line 765 {C:\BRAHMS5\brahms5.prg c:\brahms5\brahms5.exe}

Denis,

It's worth a shot.

I've had this unexplained c..005 error (not due to upgrading), and solved it by deleting the foxuser.* files in the startup directory of the pc.

If this solves the problem, you may want to set resource off somewhere at the top of your main(). The disadvantage of this is that the sizes of the report preview windows will not be saved. But then, who cares ?