>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>
For example run a STD() function over a table and compare this with native code. You'll find no significant difference
>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>

Walter -- I mainly agree with everything you are saying, but I have worked on statistical apps, and while VFP has a richer language set than some languages, you simply have to sometimes roll-your-own. In this area, a native compilation option is great -- although you could also, IIRC, have someone write in in C and build a library.

As for the issue of speed. (Not directed at you, per se, but just overall to the thread). Outside of local data-crunching, in which VFP is much quicker, and the native-code stuff we've already discussed (to death), I think any differences often are negated by programmer techniques/skills. I can tell you right now that I have seen a large and complex VB app whose screens load *much* quicker than simialr screens in a large and complex VFP app. But, this was not VFP's fault -- the framework and the code behind it stunk. If those same programming techniquies had been used in the VB app, it would have been slow too. See what I mean?