>A little background first on the layout of the departments libraries. The master class libraries are kept on a network drive. Most apps are developed on the developer's local drive. Within each project are app class libraries based on the master libraries so each app references the master classes and the developer can tailor the subclasses to the app.
>
>A problem came up where Developer1 was getting errors when modifying a class which said that the vcx "...cannot instantiate class..." and the path in the error message was showing the app directory for Developer2. As if the library compiled in Developer1's app belonged on Developer2's PC. We found a directory reference in the ClassLoc fields of a couple of master libraries which suggested that Developer2 must have modified them without knowing. We changed them to reflect the master library directory and everything was fine for Developer1.
>
>Now the current problem... Developer2 is getting the "...cannot instantiate class..." and also a vcx "...is in use and cannot be modified." error when modifying one of the app libraries the first time into a foxpro session or after everything has been cleared and released in the environment. The directory stated in the error message is Developer2's so it's not exactly like the first issue was, but since the app library is local to Developer2, how could it be in use? It's as if Foxpro won't let go of it. And it sounds to me that we have some problems with where library locations are being referenced in the subclasses/projects.
>
>I know this was long-winded, but I needed to make sure everything was covered. I don't know near as much about class libraries, the significance of the locations and how they interact with the Foxpro environment as I should, but I need to resolve this as best I can at the moment... Thanks!
>
Renoir,

One suggestion might be to issue a CLEAR ALL when done. This can help under some circumstances where VFP isn't properly releasing things.