>The fact is, VFP - being the only odd ball in the box should be removed for that very reason. It simply does not belong.

So MS shouldn't be pushing it as Middle Tier quality? Is its functinality not accesible from the VS shell? I still don't understand why you want to "dumb down" the developer's suite, it only makes sense tomake itmore versitile, or s that too logical?

>Most folks that employ VFP solutions will not stray outside to .Net.

And most people that use VB probably dick around with it on the weekend. I'm betting the ratio of VFP developers that use more than 1 tool is eqaul to the VB developers that do too. Do you have any facts? You made the claim.

>And, most folks that employ .Net will cede to VFP for some part of the app. VFP and .Net live in distinct/almost mutually exclusive worlds.

So? THat makes the product (Visual Studio that is) more robust. But then, MS has its golden chains on you, so there's no use convincing you that there's another method to designing an application.