>
>Yep, that's clear alright.
>
>Since Microsoft doesn't talk publicly about bug reports, for instance, then a MVP can't.
No. Microsoft has lots of bug reports listed on its web site, so it does talk about them.
>Since Microsoft talks publicly about not making VFP a .NET player then a MVP can talk about how bad it would be for VFP to become a player in the .NET arena.
Nope. I have the right to make my own decision either way on this. My opinion is my opinion, not that of Microsoft. If I want to lobby for VFP to become a .NET language, I can do so.
>Since Microsoft talks about OLEDB and ODBC as THE ways to access data in the future then a MVP cannot discuss any need for a .NET language endowed with a data engine of its own. And for the same reason n-tier is the flavour-du-jour when it comes to architecture. And it goes on and on and on...
Actally, Microsoft does not talk about ODBC as a way to access data in the future. It says OLEDB is the way. As for a .NET language being endowed with its own data engine, it isn't going to happen. If you were to undertake a serious study and learn how .NET is designed, you would realize why. Finally, it isn't just Microsoft that is proposing n-tier architecture. It's coming from Sun, IBM, Borland, Novell, and other companies.
Craig Berntson
MCSD, Microsoft .Net MVP, Grape City Community Influencer