>Well, I don't know what to tell you then. We've always used several .VCX libraries with just form classes in them, but have never had any problems with those. However, there is no relative pathing in them either. All of our class libraries were in the same folder, so never had a problem.

I said, the relative path is in the form, i.e. the .SCX
In the class library, there is no relative path either. We too, have all our classes in one folder.

I notice you're trying to go UP your hierarchy to 2 levels above. Maybe that's causing VFP's confusion. Could you possibly try moving all of your class libraries into the same folder and rebuilding and see if that helps? You might be better off going down the hierarchy (below your current folder) rather than than trying to go up.

This is our folder structure:
x:\foxv\classes\ - here we have all libs, users do not see this
x:\foxv\app1 - app1 folder, contains mainly data
x:\foxv\app1\prog - app1 programms, contains prg, forms, etc.
........................
x:\foxv\app99 - app99 folder, contains mainly data
x:\foxv\app99\prog - app99 programms, contains prg, forms, etc.
So, when we create a form we are in app99\prog, and the relative path to the form classlib is '..\..\classes\'
Again, does the path matter after including the library in the project? And, if it does (because the SCX stores it) how would you prevent storing the path in the form's classloc field?