>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.

This is completely incorrect, there has been no announcement publicly and no discussions within Microsoft that the next version of VFP is the last version. The only way to help solve this problem is for you to provide me with the names of the Microsoft employees who stated this incorrect information. That is the only way it can be corrected in the short term. In the near future, all Microsoft field people will received information in their mail slot about VFP 7.0 in a printed color brochure, and also get summary information about Microsoft's strategy and commitment to VFP. If anyone at your company is in question about this, forward my comments to them and make sure they view the Steve Ballmer video clip on VFP 7.0 at http://msdn.microsoft.com/vfoxpro.