>SNIP
>>Exclude the Debug Info when compiling the EXE.
>>
>>Class design is also important here - they should be designed to promote reuseability not only across projects, but within the same project.
>>
>>EXE size is a problem for the programmer to fix - not Microsoft.
>EXE File compiled in POWERBUILDER / DELPHI is much smaller than VFP no matter how huge the application is. IMO, MS has responsibility because they are the producer of VFP. Big EXE file is much slower to load. I am thinking of an OVERLAY file just to make the load much faster...
>
>>
>>>VFP application executable file is too big. You could just imagine 1 application exe consumes 15 FDD. How we wish MS could fix it in VFP 7.0. Or is there remedy on this now?
>>>
>>>VFP Database Security is still an issue. Is it included in VFP 7.0?

Hi Jess,

The size of an executable is often dependent on things other than compiled code. Everytime you add a graphic resource, for example, it must be built into the exe. If you include reports and/or tables built into the app the same is true. This can greatly impact the overall size of the executable.

Secondly, tokenized p-code (which VFP generates) will not necessary lead to larger applications. In fact, in most instances, it's been my experience that the opposite is true.

Thirdly, because of macro substitution, if VFP did produce a native compiler, it would have to include the entire run-time library.