John,

>Yup...it's linked in. What I used to like about Clipper was that you could link only the libs your required and that you could extend functionality by linking in 3rd party libs.
>
>Though, sometimes you got the little tiny EXE and big mama OVLs :-)

I may agree that sometimes including the runtime into the exe might be preffered. I also agree that it would be nice if we've got more control over waht to include and what not, but in either case VFP should remain PCODE interpreted.

But overall, i'm pretty comfortable with the way it is now.

BTW, John, did you ever look into a VFP application exe trough notepad or something. It's really interesting that it contains so much garbage. Seems like that the VFP team could improve much when it comes to reducing the size of the EXE.

For example: The exe contains comments, useless properties like the left,height of a cursor object, property settings in ASCII format, useless spaces etc.

Walter,


>>This is not entirely true IMO. Clipper can create standalone exe files,but sure is not compiled in native code. The trick is that the runtime library is contained in the exe file.
>>
>>BTW, FoxPro 2.6 for DOS can do exactly the same thing.