Olaf,

I don't believe what you say is true in this case. VFP is just simply going to read the methods memo field to know what to display. I think VFP gets confused when the objcode memo has become out of synch with the actual code in the methods memo.

After any manual manipulation of a vcx/vct or scx/sct one should issue a COMPILE CLASSLIB/FORM just to get everything straightened out.

>the class designer/editor seems not to parse the methods memo to tell which lines it should display, when you edit a method. The objcode memo seems to contain the offset and length of the text in the methods memo to show for a certain method.
>
>If I create a form class in a new empty vcx and add the line
>

>* The Load event
>

>in the load event and the line
>

>* The Init event
>

>in the init event, then open that vcx as table and modify the methods memo to contain
>

>Procedure Load()
>* The Load event
>* is now longer
>EndProc
>Procedure Init()
>* The Init event
>EndProc
>

>then reopen the form within the class designer/editor I see the line
>

>Procedure Init
>

>within the init method, while the load method seems to not have changed.
>
>Because compiling updates the info within objcode, the false display of methods is healed. And because the compile is based on the methods memo source text alone, if you didn't touched it within the project manager this could even repair what you thought has been an unrecoverably corrupted vcx.
>
>Bye, Olaf.