Thanks Nancy,

I know the class still being in memory was the cause of the problem. I just don't understand why VFP doesn’t handle this "still in memory" and "save to file" conflict in the IDE. It seams to me a problem with the potential to totally wipeout all class code would be and should be handled by the IDE. I have always caught the “still in memory” problem myself but it is pretty damn easy to forget if your deep into coding and testing.

Thanks Again,
Bill

>>Can someone explain to me how VFP 6.0 running on NT 4.0 service pack six deleted all method code in a class I have been working on all day!! All assign method code as well.
>>
>>I was running the application, extied the application, opened the class to add one line of code to an empty method, saved the class and run the application again. The class had none of the functionality it had previously. I exited the application and opened the class to find all method code gone except the one line of code I had just added.
>
>What happend (probably) is that when you modified the class, it was still in memory. Um, that's not quite what happens, but if you CLEAR ALL before modifying, you shouldn't have the problem.
>
>If you _do_ every open a class and see that method codes is missing, close the class w/o saving it, do a CLEAR ALL, and reopen the class. You *should* see your code back.