Clark,
You can exclude anything from the EXE if you are sure you include the code (and its path!) when you distribute your app. You can also call another EXE or APP so you can split up the big EXE that way. When you do, look carefully at your libraries, forms, etc. If you have forms, menus, prgs, etc. that are used in only one area of the program, separate these out. Baseclass libraries will be needed in each EXE, of course, so if your overhead is in your framework this isn't a good approach.

Another possibility is to go into your DBC and each VCX and PACK them to reduce their size as much as possible. I've seen EXEs drop remarkably in size this way.

HTH
Barbara



>The execuatable for our app is about 4.5 Mb at present. When we make mods to the app, about 600 computers retreive the new EXE from a server, some via private network other by dial-up network. We have a startup.EXE on each of the CPUs that checks version of current large.exe and compares to version on server, if server version is newer, it is downloaded to local CPU. My problem 15-20 minutes via WAN ( slow as crap ) who knows how long via modem.
>
>The exe is compiled from project that includes classes, forms, reports,menus and programs ( I beleive stored procs from DBC also )
>
>I have been told we can choose not to include reports in EXE so that when we modify a report, we just send that report out rather than a new EXE. That would decrease the size of the EXE !
>
>Could we split the large.exe into several executables ?
>But if we could, wouldn't a form in one EXE based on class in another, just compile that class into same EXE anyway ?
>
>Anybody got any thoughts or suggestions ?
>
>Thanks CB !