>>If the interaction between modules is clean and well-defined, so that separate 'applications' can clearly be seen, you can compile each as a separate .EXE or .APP, and then have a main executable that calls them as appropriate that handles the 'single main menu' and provides the underlying support structures for the whole application.
>>
>>This is a common approach for other large applications, especailly where there are clearly separate (and preferably, marketable!) modules like accounting systems in the comemrcial environment.
>
>I did a quick test and what happened when I called another .APP was that it returned to the READ EVENTS in the calling .APP. The result was that it was no longer able to reference the forms and programs in the called .APP.
>
>How do I get the focus to stay in the called .APP?

The form controls the context, so there should not be a problem here. You can launch a modal for a given sub-project project if you want to retain focus in the sub-project to prevent bouncing up to another sub-project.