>Dragan, my explanation explains what I went through regarding common classlibs and might not be exactly the same as your situation, but I think the common point might be that the first time you instantiate a VFP classlib is that becomes the 'classlib of record' that all other instantiations use statically.

I actually did try that, built two objects from the classlibs it couldn't find, didn't help when I tried to launch the standalone scx (and one of the classlibs was in its folder, it couldn't find its parent classes).

>So, we re-factored to instantiate the common classlibs in the main EXE into either public or private variables that were persisted for the duration of code execution. We didn't need to include any forms in our Main EXE.

Well you had a small main exe and bulk of the rest in the separate apps; my problem is the same but in opposite proportion. I have a huge exe (20+ megabytes) and just one form with a set of containers, one of which would be picked and shown on it, depending on a parameter (and then it would have its own subcontainers with controls).

I'll most probably give up on the idea of having an app file of it, because of exactly the bloat you mentioned. I tried, but the entanglement is nearly endless, project manager found, off the bat, about two dozen classlibs, forty prg files and fifteen forms, just because they were mentioned somewhere. So this will most probably be distributed as a zip file with vcx etc inside.

Meanwhile, I did save the form as a class and now it all just works, the form comes up without errors.