>>Sounds like the compiled code in there got screwed up. This ought to fix it.
>>I don't have to tell you, but for the lurkers backup first
>>USE myvcx.vcx
>>BLANK FIELD objcode ALL && not methods
>>USE
>>COMPILE CLASS myvcx
>>
>>How it got screwed up is another question - maybe the compile hiccupped when the class was saved.
>
>I'll give it a shot, but I don't know why the compiled code would affect want I'm seeing in the designer. They're separately stored entities, and the compiled code is generated from the text, not the other way around. I've already tried a PACK MEMO and PACK with no change.

Here comes a SWAG.

I've seen this sometimes, specially when I hacked the .vcx to stuff a different ClassLoc or class name (and some lines in Reserved3 got hosed, being now wrongfully marked as proprietary when they existed in the new parent class, or vice versa), not implying you did any of the sort - it's just the symptoms are more likely to appear in those cases. Seems to be it takes the info about the line numbers, or rather offsets into the methods memo, from the compiled code (i.e. whatever you have in the objcode memo. Now if this get fouled up, you get a technicolor mess like this. Blanking objcode and recompiling actually forces the compiler to use the text to build the objcode, and thus update these offsets.

End Swag