>>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.
>
>Ivan,
>
>I have a large number of applications for which I distributed the forms and calss libraries and reports separately and there isn't much of a problem. I do remove the source code and have never had any client mess around more than once. The first time they try it the whole system becomes non-functional and they ahve to call me to get the files restored, once they have done that they don't seem so tempted to try it again.
>
>I have no idea how to accomplish what you are trying other than what I suggested. Perhpas you need to add the VCX's to each project so they get built into each one.

I think that I will have to build them into each exe. I too have distributed report formats and such to clients with good results but in this case the program will be distributed widely by my client to their users and I would like to avoid adding to their support calls and costs if at all possible. Thanks again for your help.