>You could make the same argument about writing an ntier application with ADO or XML. The code is almost the same, why choose VFP?

If you want to take advantage of VFPs features (inheritance, cursor engine, string speed, loose variable typing, macrosubsition) then choose VFP.

Unforutnalty, NONE of those features are in VB (and besides it getting inheritance) none will be in VB.NET or available on the CLR.

You're crusade for this compile time option is the equavalint to crusading for being able to write a VB app (no more, no less) with VFP that runs on the same runtime.

While we're wasting time and money adding this, lets make all of VFP commands pig-latin versions of VB functions, its pretty much the same thing, its jst syntax.