>Next year, the in-house application (written in VFP 5.0) that I and a small staff of others help write and support is going to get a make-over. The compiled application is getting very large (almost 2 meg) and we're thinking about breaking it up into separate executables, with the main one called the other "sub-programs" when needed.
>
>Is there anything we need to keep in mind while evaluating the possibility of doing this? Any suggestions on how to make it as easy as possible? Any words of wisdom? Any and all help would be GREATLY appreciated!
>
>Thanks in advance for your help....

I would leave it as is. 2 MB is not very big for an app. You also do not get linear reduction by splitting an app into multiple apps. The reason is, you will usually need to compile common files [like classes] into each app.

At one point, I only had a shell of an app and provided all classes and forms [all stripped of the uncompiled code] separately. Performance went to hell. When I changed and started including all the forms and classes in the same APP, performance came back.

The most splitting I have done is providing all reporting functions in a separate APP which is called by the master APP. I also provide the FoxFire APP separately, but that already comes as its own self-contained APP.