This sounds like it would be a hugh amount of work on MS' part. Which I would be hard pressed to see them perform for 2 reasons:
1) As stated before, by removing these features, you're basically looking at VB.
2) It's obvious from the .Net initiative that MS is going full bore after the corporate enterprise market. And leaving the small to medium market behind. And as I've stated in other discussions, at least from what I've seen in Los Angeles, VFP doesn't play in the corporate enterprise anymore.
PF
>
>You'd probably give up data-related commands, macro expansion, and certain dynamic runtime features just for that compile option, but would keep the full product for other compile options.
(On an infant's shirt): Already smarter than Bush