>I then opened the VCX as a table and looked at the ClassLoc field which also showed the bad class.
>
>I opened again in the CB and it was showing what I saw above. As If there were two values somewhere in the VCX.
>
>So ????????

One trick to try is to Set Classlib To OneClassLib, Set Classlib To OtherClassLib - I'm not sure of the order, should the right one come first or last - before compiling. That is, if they are in the same directory. If they're not, Set Path so the good one is in the directory that comes first.

When VFP is looking for components, it has a certain order, so if you serve them in a specific order, it should take the one you want, if only you can guess the proper order.

I've had this problem with ProMatrix - they have had this up to version 6.0b (didn't try later versions), where the immediate parent class and its parent class had the same name. VFP doesn't let you do that directly, but Class Browser allows such a rename, in a way. At some point my forms started inheriting from the grandparent instead from parent class, even though the parent class was in the same directory, and grandparent far away.