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

Thank you. I will eagerly wait for developments.


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

I should receive my MSDN subscription wthin a couple of days thus will be in
a better position to evaluate all the tools in a few weeks.

I use VFP, VB, VC++, VBScript, VBA, JScript, Oracle Designer, Forte,
Uniface, Natural, and Assembly depending on the project. There are
occasions where I would prefer to use VFP as an alternative to VB or
Powervbuilder but I am usually shot down by management. No matter how
much I try to educate management, I still need a receptive hear and an
open mind to hear and understand what I am saying. I shouldn't complain
too much because I usually put in front of interesting challenges...

Daniel