>I think I'm headed in right direction, found the same as what Barbara replied to be true, looks like it just takes a little thought as you can call functions and routines from other EXEs, where it gets tricky is objects because if you have a form in the EXE it compiles the class it is based on in the EXE also, so if I have two forms based on same class and put formOne in 1.exe and formTwo in 2.exe the class is compiled into both EXEs.
>
>The actual size was not my biggest gripe, but manageability, I hate making a small change to one class, form, menu etc and having to replace entire EXE.

So what? I'm regularly uploading 5-6 meg sized exes, which turns out to be the only time I'm guaranteed to be entitled to a smoke break :).

One solution would be to keep the classes in a separate app, and CreateObject() your forms, i.e. don't use the .scxes at all. That way the classes won't get into your exe. If they do, you could mark them as excluded, relying on the fact they'll be available at runtime... think of it, you can try that right away. Mark 'em as excluded, build and try to run, just Set Proc To OtherExe (or set ClassLib to OtherExe, whichever works).