>>>>If you include all class libraries in a project, then compile it to an .exe, why would the .vcx be in use when you run the .exe??
>>>>
>>>>TIA
>>>
>>>I ran into the same problem today! I couldn't figure it out either.
>>
>>So then there is no way you can separate development from production in VFP?
>>
>>We didn't have this problem in FPD/FPW - if anythig was included in the project, you could freely modify (improve?) that, regardles of users running the compiled app/exe.
>
>I would imagine that the exe is looking in the path first and opening the vcx - move the exe to another directory, and it will not find the library files in the path.

Why would that be? The whole point of compiling a vcx into an exe is to reduce disk IO and get things in memory faster.