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.

How can we make this happen? So many 3rd party shops are vested in connection tools, What would or could MS say to them? It seems like such a small thing. I don't know why it has not been done yet? We know MS has a history of repackaging ideas, why haven't they done this? It almost seems like some kind of arrangement is in play to forclose the prospect that MS would build a product that would certainly offer benefit to the entire development community. We would have some choice SQL or ISVFP (engine). VB developers could use it. Powerbuilder developers could use it. I would not mind developing systems entirely in OLE script, providing I had the ease of design and implementation afforded by the very powerful (and quick) Rushmore Engine.

Don't write off VFP. Computer Associates (the Clipper Guys) recently purchased SBT.