>That's what wconnect.prg (in wcdemo.app) does. It loads all the libarires. I think that that should work, even if you instantiate from the outside. Once SET CLASSLIB is called and that worked in the running VFP instance it seems like the class should be invokable from anywhere - in the APP and out.. But it doesn't.
>
>It seems in order to get THAT to work you'd have to have a factory outside that does the approprate SET CLASSLIB TO IN wcDemo.app ADDITIVE which is pretty lame. I'm pretty sure some other libraries do this and it works (like the GDIPLUS library)? It could be that this happens because the classes have a relative path location (.\classes) rather than being at the root project level...
>
>Fortunately this is not the scenario I'm after - my scenario is actually just to bootstrap a class in the .App file and I got that to work with Hank's tip. See the other message in the thread that also shows what I'm doing a little more clearly.
>

Remember putting some code on the stack in 2.6 days to add them to the searched pool ?
If you have classes with base classes in other app/exe, this approach helps.
Sometime the age shows - speaking of vfp of course, never about us ;-)