>What needs to happen - is someone needs to convince MS to Build a VFP Server engine (much like the BDE Borland made) that could be licensed just like SQL and others. This package would need to contain all components necessary to provide security, connections and transaction between a VFP desktop program and ISVFP Server Tables, without requiring a VFP developer to build or purchase 3 party "classes". That is what needs to happen.

Hi Terry,

The vast majority of developers are quite happy with sql-server, which does everything you're mentioning. Why would MS want to reinvent their own product? Then, why would any developer want to use this "thing" as opposed to sql-server?

I think that what really needs to happen is that vfp be removed from vstudio. The other two languages in the suite (C++ and VB) are "pure" languages - if you want to add functionality to them you get third party tools (crystal, sql server, etc.). VFP is really more comparable to Access (it's all self-contained) than to VC or VB.

Alex