Olaf,
I don't believe either one of you. *g*
What I believe is that VFP detects an error condition between what is in the two memo fields and that's what causes the blanked out methods editor window.
VFP does a simple parsing of the methods memo to figure out what is where, it doesn't use pointers from the objcode to get back to the lines in the methods memo.
>>VFP isn't going to decompile the objcode.
>I didn't say VFP decompiles objcode. I said it uses some offset/source code length stored within objcode to find the lines within the methods memo.
>
>If you don't believe me, simply try what I said and see for yourself. Or maybe you believe Fabio Lunardon, quote: "VFP uses ObjCode to find the lines of code...".
>
>I tried now in VFP9 and 7 with the same result. And after I cleared the objcode memo, the class designer/editor wouldn't show any code, although the methods memo isn't cleared. So it must use offset/length informations stored within objcode to determine what bytes of the methods memo to show as a certain method within the editor instead of finding Procedure
and diplaying the following lines up to an Endproc line.
>
>Maybe it is done to prevent the word "Endproc" or the line "Procedure " within a method (think of comments) to mess things up. And as I didn't change any of the of the reserved fields while hacking the vcx in table mode, there must be the observed link between the methods memo and the objcode memo and no other field.
