>Hi Jim,
>
>You are probably right about customer centric vs. MS centric, I think what John's basically saying is MS has heard all of this stuff from the FoxPro community since day one and it's changed little if anything at all in their course of action. Basically in the grand scheme of things, VFP is simply not significant to M$ from a revenue standpoint and further attempts at slamming the marketing, asking for features that we've been denied for years, etc. are futile. I think the basic message is get on board and play in this new world of components or else look for another vendor who's still interested in making the all encompassing tool. I don't necessarily like this message and I'm not sure I buy it entirely, but the records does pretty much speak for itself.
>
>The problem is that apparently no one at MS outside the Fox team realizes that VFP is a great tool and that if it were given equal attention and equal billing it could easily supplant VB or basically render VB useless. From a technical standpoint VB has very little on VFP, but MS certainly doesn't want to kill off their bread & butter product in the hopes of moving everyone to an up & comer and they really can't be blamed for that. Personally, I think we would be best served if the VFP DML, the VFP Object model, & OOP along with some of the things that are nice in the VFP IDE compared to VB were put into VB and Fox was just killed off.

I agree, that but I seems impossible because a total rewrite on VB kernel.