Hey everyone!

Some of the threads being posted about MS lack of commitment to VFP and Tech-Ed have got me to thinking about VFPs role in the VS world and how we should be thinking about the product:

We've got to stop thinking of VFP as a primary database development tool. It's obvious that MS has Access on the low-end and SQL Server on the high-end slated for those roles. What I propose is:

The Second Big Fox Paradigm Shift: A redefining of how we use Fox similar to the adjustments we had to make when VFP was first released. What we have to focus on now is VFP as a RAD/OOP development language. Forget DBFs. Use the DBC as a data wrapper for SQL Server or Oracle data. Make virtual 3-tier applications with VFP on the front-end and VFP COM servers in the middle working hand-in-hand with MTS to an enterprise database.

The DBF file format is a noose. Dump it. The Fox Database is dead, long live Visual FoxPro!