Hi David ----

While we both have the same goal, I'd like to add to some of what you're saying
>
>1. VFP is the best database development tool MS has.
>
Stop thinking of VFP as a database dev tool. Start thinking RAD/OOP tool. If you can pitch VFP as an OOP front-end in client/server AND native database apps, you'll carry more weight with management or client.
>
>2. The DBF file doesn't carry much weight in IT these days.
>
Boy, you got that right. And deservedly so.
>
>3. MS would support VFP more if it sold more.
>
>4. MS would support VFP more if it helped them sell more NT licences.
>
Ummmm....I think not. VB will always be king with MS. When MS bought Fox Software, there were far more Fox developers than there were VB developers.

>Here is the solution:
>
>1. Don't buy VS (VFP usage is hidden from MS).
>
Now that is wrong-headed. The other VS tools allow us to prove that VFP works and plays well with others. We can very rarely pitch VFP as the total solution these days and to shut out the other tools is silly. Anyway, if MS saw a big upswing in the number of solo VFP licenses, they'd (rightly) assume that the VFP crowd was still on a "technical island" and this would further give MS reasons to isolate and kill VFP.
>
>2. Buy 2 copies of VFP 6.0 (one new licence, one upgrade).
>
Sure thing....send me $995 ;-)
>
>4. Write to MS requesting a SQL Server engine as well as a DBF one.
>
No no no no no. There is a version of SQL Server coming called "Embedded" or "Personal" that will allow you to use SQL Server as your engine without the need to have a server based copy. Accessible through OLE-DB, ADO...whatever. You already have the capability to use SQL Server on the back-end through ODBC, VFP6 adds ADO to the mix (although you could also use ADO in VFP5).
>
>Here's the result:
>
>1. MS will market VFP more 'cause sales are increasing.
>2. MS will commit to VFP 8.0 which will be VB with VFP database tools.
>
>
Oh no...not the perpetual "VisualFoxBasic" rumour again!!! Seriously, I think VFP is evolving more towards a RAD/OOP xBASE tool that may, if anything, be eventually divorced from the DBF native structures. If you can excuse the "fat client" there's nothing as a c/s front-end that VB can do noticeably better than VFP and THAT is the word that should be spread.