>Fatal Error C0000005 is apparently a well known bug associated with the release of a form. (I found two references in the MS Knowledge base).
>
>I currently use a Messagebox in an error processing procedure which is the target of an ON ERROR command. The specific error that causes the problem is an attempt to edit a record using @...GET while that record is currently locked by another instance of VFP on the same machine. (This is how I debug my shared access code when nobody's around to run on another machine). My code allows the user to retry, but before it gets a chance, the fatal error...C0000005 pops up.
>
>Judging by the articles in the knowledge base, this error actually happens when the messagebox is shutting down after I hit the button that elects to retry.
>
>I am currently running on a very small budget trying to shoehorn some very old FP code into VFP and I simply do not have the time to rework everything into the new OOP model.
>
>Is there anyone out there who knows enough about the "C000005" problem to give me a quicky fix that'll still allow me to use a messagebox in an error procedure that's triggered by an @...GET?
>
>Is the "C0000005" problem fixed in Service Pack 3?
A huge number of the C5 errors are fixed in SP3.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer