>>>Just as a note, I'd seen this sort of problem occur when I bring in stuff from another program (say, an older program) into the project. This imported stuff (e.g. forms) may contain references to an older VCX. When I build the project, the references to the older VCX will get pulled into the project. In such a case I have to go into all the stuff I'd imported to remove the references (e.g. open the SCX, VCX, etc. as DBF and change the references to the older VCX within the classloc column to the newer one).
>>
>>There's actually potential trouble in how you bring the additional classes into the project. It's literally decided by the relative path of the class on which you build a new subclass in a vcx which will be in the project. Wherever it is at the time, the project manager will find it (because _you_ found it when you created it, and the path is stored in the classloc memo) and include it in the project.
>>
>>Which means trouble if you brought in a class from, say, sister project or backup, which are supposed to be built on the same parent class, but at the moment when you brought them in (in whichever way), if the class you're building is based on a class in a different folder (specially when copying between two instances of class browser, or add class ... from [some path]some.vcx), its classloc will contain path pointing to the parent class of the source class _from_ that folder... IOW you get an overly complicated mess with paths.
>>
>>The only way I found to avoid the mess was to copy the source class library, from which I wanted to copy a class into my vcx, into the same folder where the targeto vcx will be (assuming the parent classes for the source vcx exist in the current set of folders, i.e. it's the same framework, same relative paths within the project), under a different name (if they're accidentally the same, as happens when you bring a class from the previous version of your app). Then Add Class or copying between two instances of class browser works, without complicating the paths.
>>
>>Don't forget to discard the source copy - once used, it becomes clutter.
>
>What I did in the past is to completely remove the library path from the VCX file. You can open it as a table, scan and remove the relative path. This assures that only the current project library is used.

Sure, that's how you do it when extra libraries have already found their way into the project and you have to clean up. The procedure I described is applied before and instead of that, preventing the inclusion of extra libraries.