>
>1. VFP is OOP which is a more efficient model (easier to build with and maintain).

Not valid with VB.Net, which is fully OOP.

>2. VFP version 7 is released and is built on a solid foundation. VB is going through a major rewrite. DotNet is in beta.

VB.Net is a total rewrite. It is essentially a version 1.0 release.

>3. VFP has 3rd party tools that enable web interfaces now.

VB.Net will support Web forms. I haven't played much with them, but I've seen some complex examples... they are very cool.

>4. VFP is flexible with nTier (can build COM/DCOM - or it can use VB COM/DCOM)

This is the whole idea of .Net. You can easily create n-tier apps and web services.

>5. VFP is data bound which makes it easier to build against databases.

Not necessarily. You talk about n-tier, which throws out remote views and SPT. You'll have to go ADO or XML. I don't think VFP provides an advantage here.

>6. VFP has a more robust development language.

Can you clarify this?