>The main problem I face when trying to sell VFP as a development tool is
>managers perception. The general perception is that VFP is playing catch
>up to th other tools and thus not worth using. VFP7 adds Intellisense, VB
>had it for years... VFP8 adds AutoIncrement, Access had it for years...
>You see the pattern.
>
>AutoIncrement has its place but it's not big deal to most developers that
>currently use the product and it certainly won't be a selling to me or
>my client managers.

Please don't consider AutoIncrement a major feature of Toledo, it is just one in a small list of things we decided to show before we disclose all the details at a later date. AutoIncrement may get a small mention in a detailed list of new features, but it will not make the line item list on the box listing the new features.

VFP 7.0 has many things VB (VB6 and VS .NET) does not have - like - data driven fully customizable IntelliSense (FoxCode.dbf), and many VS .NET groups like C++ and VB .NET teams have seen this and drool over how cool it is. VFP has a local data engine, VB does not. VFP has great visual subclassing of components at all levels including full containership, VS .NET and VB6 do not. Even the VFP command window is better than the new one in VS .NET. You will not see Microsoft compare developer tools side by side, our goal is to sell MSDN subscriptions that contain VFP, VS .NET, VS6, Windows, and more, then have developers use what they need. If you want to compare VFP to other tools, I think you have lots of information to do so and educate those who you talk to who need to be educated.