I never seen this happen. Regardless how I close Class Designer all my changes are always saved.

>Description:
>
>Though different means exist, from the project a class can be double clicked in order to edit it, and the Class Designer Form appears. From the Properties Form a method can be choosen, and double clicking it will popup the edit form for it. Btw, this last step can be done repeatedly, and this way several methods can be adjusted.
>
>In VFP5 (don't know about 6), it would suffice to cross away the main form of the Class Designer, and VFP would ask for the class to be saved, and a Yes would ask for the subsequent methods whether you want to save them. Btw, a small bug existed in VFP5 because it would ask this also for methods which weren't adjusted.
>
>In VFP7 this small bug has been solved by means of just not asking for any method whether you want it to get saved, and it asks it for the class itself only. I accepted it as more friendly.
>But sadly, it doesn't save the methods ...
>
>Solution:
>
>Cross away each of the individual edit boxes.
>
>Remark:
>
>I can't tell which situations might exist that the methods are saved after all, and I am pretty sure it can. It looks like some status can arise that it doesn't work anymore.
>As other *Compatibility report* threads show, I expected this to happen because of running VFP5 over VFP7 compiled classes. It is 100 % sure now this has nothing to do with it, because really nobody touched VFP5 during the process of encountering the above as described. IOW, the basis always was VFP7-compiled VCXes.
>
>BTW, at the question of "Save Class xxxx" and a Yes, the methods of the class WILL get saved. In the former version that is. The deleted records in the VCX, together with the new timestamp shows this.