Mark and Rich,

PMFJI. I've always used something like Mark's approach. I determined the following requirements:

1. a Pre-launcher that copies updated App's, Exe's and other stuff from the server, then calls the module manager.
2. a module manager that calls each of the APP's in the collection, instructing them to run their menus (I used a large combined menu tree). Even if you use a different menu system from mine, it is crucial that the individual apps somehow register themselves, so that you can maintain modularity. The module manager should be able to run any module, and any module should be changeable without changing the module manager. I found that having each app set up its own menu pad was the easiest way to do this.
3. the module manager then executes READ EVENTS. The menu options set up by the individual apps all call their own apps.

Some notes:
VFP by its nature does not support modularity. The practical result is that the class libraries in your module managaer are not visible in the apps. Moroever, there is no way to "SET PROCEDURE TO MyApp.APP" or in any other way make the contents of one APP visible to another. Therefore, each of my modules has a redirector, so that menu calls do something like: "Do Ar.APP with 'customer.scx'" The redirector receives the name of the form, which is only visible once code is executing inside of the app.

Another strange consequence of this lack of visibility of class libraries is that I had to replicate the general-purpose class libraries in each app!

I abondoned this approach in my VFP 6 framework, concentrating instead on the other techniques that were suggested here, such as excluding bitmaps. I've also vastly streamlined my classes, using a single INIT routine called by all controls, stuff like that.

Hope this helps.



>>Thanks Mark, those ideas will certainly help. I would still like to know if there is a way to have sub projects called by a main project.
>
>You can have a VFP APP call another VFP APP. Therefore, each sub-App can be its own project. I do this where I have ageneric App launcher compiled into an EXE. This EXE ends with DO (MyApp). MyApp is a separate project and its own app. For my own reasons, MyApp will not run by itself. It must be called by my Launcher EXE.