>Ivan,
>
>In your second exe's startup program do all of the SET CLASSLIBs with the IN syntax before you run any forms.;
>
>

>SET CALSSLIB TO MYForms IN First.exe ADDITIVE
>SET CALSSLIB TO MyControls IN First.exe ADDITIVE
>

>
>Personally, I would ship the VCX/VCT files separately from the exes and then just update the class lib that changed. If you are concerned about source code being available, you can blank out the Methods field in the VCX before you distribute it (do this to a copy because once it is done any attempt to edit the class will remove all of the code for that class).

Jim,
Thanks for the suggestion, BUT!
That seems to works for non-form classes in the class libraries but it still does not work when instantiating a form in the class library with CREATEOBJECT("MyForm") or when running forms based on a form class in the class library with DO FORM MyForm. Any ideas on how to make this work? Thanks.

P.S. I also am concerened about the stability of shipping a vcx/vct combination. After all anyone with FoxPro can open and modify, on purpose or accidentally, a vcx since it is just a table. It also means more files to distribute and worry about. Maybe I am paranoid.