Well said John! I just hope that they will change their attitude about VFP.

>Hi all,
>
>The following is what I sent MSDN. I CCed some MS people that I hope will take notice. Everyone in agreement with this? Disagree?
>-------------------------------------------------------------------
>MSDN is doing a wonderful job in creating and maintaining the XML Developer Center. It is a great resource for learning and using XML technologies. I have a bone to pick, though, with the quotes likes the following:
>
>"Custom tools for viewing XML data can be written in the Visual Basic® development system, Java, and C++."
>
>And? And?!? Where's Visual FoxPro?
>
>Visual FoxPro, a Microsoft Visual Studio member, is a database development tool ideally suited to create data services components that work with XML. It's pretty sad that I have to remind a Microsoft professional developer service of that. When MSDN omits Visual FoxPro from the list of what tools can be used for working with XML, they do a disservice to novice or intermediate developers -- especially VFP developers -- who may be unaware that an omission, and not a purposeful exclusion, is being committed.
>
>In most COM, DNA, and DOM applications where Visual Basic is a participant, Visual FoxPro can participate as well. In the future, I and tens (if not hundreds) of thousands of developers, would appreciate Visual FoxPro being included in your list of applicable tools in articles, samples, and downloads.
>
>If you have any doubts whether VFP applies to any given situation, there are many experienced Visual FoxPro developers in Microsoft's Most Valuable Professional program, including myself, and elsewhere who would be happy to check it out.
>
>Sincerely,
>
>John S. Koziol
>Microsoft Certified Professional, Visual FoxPro
>Microsoft Most Valuable Professional, FoxPro