>The company I work for (a crop insurance concern) is in preliminary stages to settle on a toolset and platform for our "next-generation" systems (3-5 years out). Yesterday we had a meeting to discuss the first draft of a development tool criteria list. The list compared VFP, Visual Basic 6.0, VisualStudio.NET, and Java tools. VFP had been given the lowest rating in criteria "Vendor Commitment" and "Future Life Span of Toolset". Even Visual Basic 6.0 was a couple notches higher in those categories.

Another point I should make to both you Joe and others who are reading this thread. If you or anyone has an issue like this in the future, it is far better to send me email directly at klevy@microsoft.com rather than posting a message about it publicly. If you truly care about the "positive" persceptions on Visual FoxPro, not posting message like this online for others to read actually go against your goes in promoting and using VFP. If anyone gets mis-information like this in the future, get the names of the people and send me email directly, that is the best way to resolve the issue. And I can contact anyone at a company who has received mis-information about VFP and set them straight on the truth and making sure they know Microsoft is committed to VFP and its future.