>Since they are in different processes, I'ld expect the behaviour you describe, since they don't share a common adress space, but I haven't really researched it. You might try a slightly different architectural approach: create the object in the main exe. If you need specific functionality only in the sub.exe, don't implement as a subclass of the main, but either create small worker objects in the sub.exe or try COM event binding. Since you'll have a marshalled COM object, if you have many calls to this object, the performance will suffer - take a look at your code seen from that perspective before trying <g>. The only other way not to suffer from redundancy is to put the common inheritance into separate prg's or vcx "left" on the disk to be called directly - but the memory will probably used in the main and sub exe, even if the code is only not redundant.

I have about 80 instances of that object with about 50-75 property defined in each as well as about 5-10 methods will with code in each. This is our biggest object. So, I guess the only approach would be COM event binding. I just don't know presently how to achieve that. Could you explain a little bit more about what I should expect to achieve that?