>>>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.
>
>Well, I'm afraid that the majority on this site develop their applications on computers that are physically disconnected from the deployment environment, so there isn’t much reaction to problems that only happen in a setting like ours, i.e. development takes place on the same network as production.
>I can’t believe though, how little response I got to the question: Why would, ever, an EXE look for a class lib, when all class libraries are included?
>I actually hoped that I'll get firm answers saying that, no, this is not possible, if you include the class libs in a project you sould never get a 'cannot find class...' error.

One thing that I had found that occured in VFP6, was that if you made a reference to ANY class that existed in an external to the .EXE classlib, that VFP could become confused and expected to find all classes externally. It appeared that it had "lost" it's internal references of all classlibs. I don't know if that still occurs with VFP7 or 8, but it was definitely a problem with VFP6, at least for our app. Could this be a problem for you, or are you absolutely sure all of your classlibs part of the .EXE?