>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.
>

I know it that I am wasting time,
however for to do a favor to Olaf
I show to you that you are wrong.

CLEAR

CREATE CLASS test OF test1 as custom nowait

TEXT TO initcode NOSHOW
? '1111111111111'
? '11111'
ENDTEXT
aselobj[ax]
ax[1].writemethod('Init',initcode)

RELEASE AX

ACTIVATE WINDOW (WONTOP())
KEYBOARD '{CTRL+W}' PLAIN
DOEVENTS

USE test1.VCX
REPLACE FOR objName=='test' AND NOT ISBLANK(Class);
	Methods WITH STRTRAN(Methods,initcode,"? 'Look ENDPRO line'")
USE


MODIFY CLASS test OF test1 METHOD Init

* remove a byte
CREATE CLASS test OF test1 as custom nowait

TEXT TO initcode NOSHOW
? '1111111111111'
? '1111'
ENDTEXT
aselobj[ax]
ax[1].writemethod('Init',initcode)

RELEASE AX

ACTIVATE WINDOW (WONTOP())
KEYBOARD '{CTRL+W}' PLAIN
DOEVENTS

USE test1.VCX
REPLACE FOR objName=='test' AND NOT ISBLANK(Class);
	Methods WITH STRTRAN(Methods,initcode,"? 'Look ENDPR  line'")
USE

MODIFY CLASS test OF test1 METHOD Init