>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?

I don't know for sure, but there must be some sort of reconcilliation of the path in order to find the library (even if it's to just ignore it). I know of no way to prevent the storing of the path in the CLASSLOC field. All I do know is that it stores a relative path.

I just looked at some of our forms, and it's doing the same thing as yours, going up 2 levels in the hierarchy to pull in classes that are common and used in a wide variety of our projects. So I guess that's not the problem.