Database support will always be through ADO, ADO.Net, ODBC, or some similar technology. VFP.Net would like very much like VB.

>I wish they'd have considered VFP.NET or some form of VFP without support for standalone DBC/DBF (ie you gotta use SQL Server or other ODBC source). I think that would put VFP in the same revenue scheme as the other tools (you're real likely to license SQL Server) and using a database engine would look better to customers.