>>FWIW, I've since discovered that when the moved class gets instantiated, the object does refer to the new library -- even though the class definition still points to the old library. So, everything works ok, just don't understand what's going on here.
>>
>>...sigh
>
>Pete,
>The ClassLibrary is a little misleading (IMO). It doesn't refer to the library where the current class resides. It refers to the library where the ParentClass resides. If the current class is a subclass of one of VFP's base classes, then the current library is displayed. WHn you moved the classes, did the location of the ParentClass change?
>
>Also, when moving classes, open all libraries and forms that have subclasses/instances of the ones you are moving using the "View Additional File" of the Object Browser. Ken Levy posted that the OB will correct all the ClassLibrary references when you move it. If the libraries aren't open, you may have to correct things yourself.

Larry,

Thanks for the response to my question. I think this will help me a lot -- I was indeed confused about the meaning of ClassLibrary. I'll spend some time today investigating the implications of your answer, and I'm pretty sure this will help a lot. The only thing I'm not completely sure of yet is that I was using the Project Manager to move the classes from one library to another, not the Object (I assume you mean "Class") Browser. I didn't know you could use the browser t move classes. But I'll look into all this.

Thanks so much,
Pete