>>
>>How big will the runtime be if it now includes the compiler too?
>
>No increase in size. The code that compiles VFP p-code for PRG-->FXP, etc. is part of the language (i.e. COMPILE) and that is part of the runtime already. FoxPro/VFP has always not allowed this. I think it goes back to the days in 1.02/2.0 when the runtime was sold separately and it was feared someone would re-distrubute the runtime with a custom command window, etc.
>
>I just checked, and the new runtime is currently 3.3M, exactly 1K less than VFP 6.0. Basically it's the same, no significant change. Keep in mind there is a new part of the runtime, a seperate file called vfp6t.dll for the multi-threaded DLLs, and it's a bit smaller, 3.0M. You will need this file for running multi-threaded DLLs (independent of single threaded DLLs, EXEs, APPs), etc.

This is all good news. And a smaller runtime for DLLs is certainly welcome. I assume that most of the size reduction is due to the UI components being stripped out.