@Matt: "Clean Up Project" packed the VCX, but my problem records remain.
@Jim: I went to make a copy and now my container class isn't showing up in the designer, even though objects within the container are still in the VCX. Clearly this VCX is just severely #$%ed up. I'm going to restore an older version and get back to work. If you're interested in a corrupted VCX I'll be happy to post it. :)

E


>Eric --
>
>Can you just make a copy of the actual files and make them available for somebody else to look at, or is the class structure too complicated to look at?
>
>I for one have not had any problems with visual classes, and am wondering if there is more information that can be gleaned from that VCX ... from what you have said, VFP seems to work OK with these VCXs. I mean, you found out about the 'bad' rows because of the GoFish, right?
>
>>They show up nowhere in the designer. Just to be sure I set their left and top properties to 0 and made sure they're visible property was .t.. And they don't show up on the property sheet or the object list either.
>>
>>I'm made a copy of this class using the classBrowser so I could post it and everyone could inspect it. However, when I did this the bad records aren't in the copy of the class! It's really as if they're deleted, but they're definitely not marked deleted. There are some deleted records in the VCX and they act appropriately.
>>
>>So, yeah, I'm starting to not trust Visual Classes either. I've been tempted in the past to create a tool that serializes the VCX and SCX files to XML for everyday use, and the deserializes it only when you want to edit in visual mode. This would solve some of the source control quirkiness as well, but from the opposite direction as it's mostly done now with _SCCText.
>>
>>Eric
>>
>>>
>>>
>>>Do the controls still show up in the designer?
>>>