Rich,
There was a thread a few days ago about FoxUser and the C0000005 error. It was suggested that you open VFP without FoxUser, then open the table and PACK it. Sometimes FoxUser & VFP get confused about what's deleted and what isn't.

HTH
Barbara

>I keep losing changes I'm making to a form's methods because of this, help, please!
>
>I always set up my design environment to save form positions, code window size/position/font, etc., to FoxUser. Have done so since FoxPro 2.x.
>
>In VFP 6.0, I double-click an object in form designer to bring up the code window. It brings up the one method I have code in, or the last method I saved code into, whatever. I decide I don't want any code in that method any more, and remove it. I put code in another method.
>
>Unless I close the form designer (saving form's new condition to FoxUser), the next time I double-click that object to bring up the code window it tries to bring up the empty method and gives a C000005 error! I lose any changes I've made since I opened the form!
>
>Is this a known bug? Is there a patch? Does SP1 fix it? Save my sanity, please!
>
>(I know, I know, just save and close the form more often! "Doc, it hurts when I do this." "Don't do that any more!" ;)