>I can't really follow what the problem is. But why not use NEWOBJECT() instead ? this function will not include the class into the project at compile time. I've succesfully called a class (in a form) from another exe using a code like this:
>

>If (_VFP.StartMode == 0)   &&
>   ** on development time, use MyClassName from MyClassLib.VCX from current dir
>   This.NewObject( 'oObject', 'MyClassName', 'MyClassLib' )
>else
>   ** on run time, use MyClassName from MyClassLib.VCX from Another.exe
>   This.NewObject( 'oObject', 'MyClassName', 'MyClassLib', 'Another.exe' )
>endif
>

The problem is that we have deployed that at a large scale. There are numerous projects and PRGs using CREATEOBJECT() for the creation of that main class object. We just cannot change that approach at this time. What we can do however is to exclude the sub class library from the EXE and store it on disk. This will require two additional files on the server but if that resolves the issue, I'll consider this.