>Also would like to ask what is the best way to communicate with SQL Server. Pass-through? Views? Or primarily using stored Transact-SQL procedures that get invoked (how?) via VFP?

That is really dependent on what you are doing. Parameterized remote views are the "easiest" way of accomplishing many things, especially data entry screens and ect. For more advanced queries, I would suggest SQL passthrough. Yes, you can implement TSQL Stored procedures via SQL passthrough functions. This is often good for more complicated inserts and etc., as you can have all of your RI stuff and etc. on the server as well as the validation code in the SP. Then, you just call the SP and "wait" for the return codes....

>Has anybody benchmarked VFP 5.0 performance against SQL server when running them on the same system?

Not really. Performance is often related to many factors, especially when dealing with ODBC connections. I have heard rumblings about how ODBC connections were supposed to be faster than Rushmore on a LAN in some situations, but I'm skeptical about that....

The advantages of a SQL server platform extend beyond simple speed. I discuss some of that in the October VFUG newsletter. There are also some good white papers floating around at the MS site.

HTH,
Scot.