>>I have a fairly large project with a couple dozen tables and forms. When I create an executeable .EXE file it is about 1MB in size.
>>
>>My question is:
>>Would it make sense to break the project into separate .EXE files? Maybe one .EXE for each form to make the program run in less memory and run faster? And let one main .EXE control the whole program. All of the DB tables would be free tables also. Does it make sense to do this at all?
>>
>>It sure is a lot of work and pretty much destroys the idea of having an all-in-one type of project environment. What do you think?
>>
>>I have been experimenting with this idea, but before I get too far I had better get some opinions. This could be an unwanted headache.
>>
>>Thanks for your inputs.
>
>Steve,
>
>I would recommend against the idea of breaking up the exe. When compared to the size of the VFP runtime files, you 1MB exe is small so any reduction in memory requirements would be insignificant.

You all are right, but, in a network environment is a lot easy
to maintain an application if it is broken in pieces. I do that,
let's say that you need to make a change to a function or report,
right at the moment while users are working , you have to make
the change, recompile and stop users from working to replace
the "exe" file, in the other hand, if your function or report
is a stand alone file, you just need to replace that file,
and you have a good chance to do it without stoping the users
from working.

Hope this helps..