James,

Thanks a TON for your ideas here. Tonight I finally decided to take the plunge. I ran SETX in the init of my old application class, added some custom methods and properties to the form that my appliation would be looking for, and I actually got it to run within my application. It's still bugging out, but I think this is because of real bugs in my form, and not in the app.

One thing I had to do was remove the default error handler in kBizObj (which fortunately I had subclassed before building my business objects). I also had to do some interesting tweaking in terms of adding libraries to my project (MM libraries which I have no idea what they do). And the final big kicker was my stub program. I had to add a DEFINE to the appincl.h.

I'm sure there will be problems, but hopefully I'll be able to migrate the whole app over to MM over the next few months. I just needed a quick fix here.

Thanks again,

David

>>James,
>>
>>This is very intriguing. The issue as I see it is running the form outside of the native MM application object. Setx will just set up the project files, right? If I run doform('newform'), it's going to be looking for application object items as it instantiates, isn't it?
>>
>>
>The reason for setx is to be able to test your bizobjs and forms outside of the MM runtime environment. You would probably need to include the basic libraries in you app, or you could try using SET CLASSLIB TO ClassLibraryName [IN APPFileName | EXEFileName] syntax to instantiate them. a little experimentation would be necessary here.