>>>In the event of a crash of VFP or Windows itself while VFP is running, I've seen cases of funky stuff ending up in .VCX/.SCX files. You might want to open the .VCX/.SCX as a table and BROWSE the Methods column, see if there's anything unexpected in there.
>>
>>That's right. And using Al's idea of finding possible problems in the VCX, you can better convert with FoxBin2Prg to text and back to binary so you have a newly VCX. Many times this convertion fixes problems without the need of browsing unneeded stuff at so low level.
>
>Interesting - did you specifically make FoxBin2Prg so it can deal with "garbage" in the Methods column of VCX/SCX?

Hi Al:

Not specifically with columns, but sometimes happen that other garbage is inside VCX binary data which makes the class behave bad or in strange ways, so taking out all the text code and reassembling the classlibrary sometimes can help fix it.

Even looking at the text version, which is more clear to look, you can find some values that can meke Fox fail, so you can fix them on text and regenerate the binary.
In example, some grid "Invalid height", "invalid position" or similar problems can be fixed this way.

Out of this, I can't say why he is having this problem, because in the posted code I don't see nothing bad.