>There is a lot of "air" in a VFP EXE. I have never conducted a scientific study, but I have seen the following... Once you get to a certain size, say over 3mb, anytime you add a class library, Form, Report, bascially anything that is manifested as a table, the EXE starts to get bigger at an exponential rate. Why this is the case, I do not know.
>
>When you recompile, VCX's, SCX's, FRX's, etc, are supposed to get packed. For good measure, I will use these meta-data files and pack them myself. Still, after a while, it makes little difference.
>
>And of course, if you can turn debug info off, do so. However, if you use some sort of error logging routine, that won't work anymore. IMO, having the debug info is invaluable.
>
>What to do? I suppose one idea, if this is a problem, is to use a small EXE loader and in turn, divide you system into smaller APP files, presuming your system is amenable to getting divided up that way.
>
>In the words of Bill Clinton, I feel your pain on this one. As for my lists of strategic enhancements for VFP in the future, getting EXE size down is one of them..

John, you are right. I broke my EXE into a main EXE and many small APPs since FP2.X. This made updating my clients' programs through the telephone line simple. However, in VFP, I have to put my base classes (based on by almost all forms) out of the APPs (or, not preferably, putting it into every APP containing forms). I have tried putting it into one of the APPs and run a SET CLASS LIB TO inside a program in this APP. However, it didn¡¦t work. Can you suggest any better solution on that?

KM