>>For my desktop apps now it's VFP9 with tons of SQL Server views and stored procedures and C# with typed datasets. I haven't created a .dbf or a .dbc in decades.
>
>..which sounds better than the way I've done it -- which is to create VFP remote views in a .dbc that connects to SQL Server via ODBC. Easy enough to do, but sounds like your way would have a lot of benefits.

I've never created a .dbc or a cursor adapter.

Early on it was apparent to me that:

- I could minimize the chance of code obsolescence by packing as much logic as I could into TSQL views and stored procedures. (The purists hate that - putting business rules in the DB - but I'm now using many of those views and procedures in C#)
- Using a few classes and methods I developed to connect with SQL server (using connection strings, not ODBC) SQL passthru let me simplify my coding, maximize performance and reduce the importance of the viability of VFP.

I still spend more much time learning and writing TSQL than I do with C#.

It seemed logical to me that MS would pour a lot of money into SQL Server and that has turned out to be a good bet.