With respect to the three VFP advantages that are continually trotted out as advantages:

>A blazinly fast local data-engine

In C/S computing, your local data sets are small, so, the fast local engine that
can work with 100's of thousands or millions of rows is not the feather in the cap it used to be.

>A Fully OOP environment where the UI is indeed the most important one.

VB 7 is going to have this. However, most OO principles can be employed anyway in VB. And, if you have liened in the way of web development, the OO benefits in UI development are moot..


>A rich data centric language including it's own DDL and DML.

Again, in C/S development, this is also a moot point.

With all of that in mind, VFP is only decisively better when talking about single tier applications

There are some advantages when discussing two tier applications/Client/Server applications.

In three tier/N-Tier scenarios, the advantages are miniscule at best...




>I'm sure you would mention early binding next. You're quite right that these are characteristics where VB wins from VFP hands-down. But to be honest this is not enough for me. In VB I don't have:
>
>- A blazinly fast local data-engine
>- A Fully OOP environment where the UI is indeed the most important one.
>- A rich data centric language including it's own DDL and DML.
>