C5 is a general Windows memory error and good luck figuring out the specific cause. Corrupted data files are one possibility so if you can rebuild your indexes or check for other table corruption that might offer some clues. Worst case would be to create a special debug build that does some logging or screen/wait window echoing so you can home in on the offending line of code. Another possibility as Dave mentioned is that the runtimes somehow went bad. Finally, is there a config.fpw file involved? That would be another place to look for environmental clues.
-- rk -----Original Message----- From: ProfoxTech [mailto:profoxtech-boun...@leafe.com] On Behalf Of Chris Davis Sent: Wednesday, March 19, 2014 11:41 AM To: profoxt...@leafe.com Subject: VFP executables crash! Hi All I am hoping someone can help with this. Up until a few days ago everything was fine. Now when I try and run any VFP executable i.e. a compiled project it crashes with ... Fatal error: Exception code=C0000005 @ 03/19/14 03:35:12 PM. Error log file: C:\Program Files (x86)\Common Files\Microsoft Shared\VFP\vfp9rerr.log This is both my own exe's and also those from other sources. Thanks Chris. _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/DF1EEF11E586A64FB54A97F22A8BD04422A71AF988@ACKBWDDQH1.artfact.local ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
