You say you wanted to sound like you know what you are talking about:) SPT can only use ODBC and VFP have known problems using ODBC driver and new datatypes. I would suggest using OLEDB with CursorAdapter.
PS: As per the driver you would supply them both 32 and 64 bits SQLNcli+.msi files downloadable from MS downloads. It installs both ODBC and OLEDB drivers on client. 32 bits driver wouldn't install on SQL server 64 bits installation.
Cetin

>I don't use CursorAdapter at all; my application is built on SPT. Thank you.
>
>>I did some extensive testing on this for my presentation at the German DevCon last year. I tested ADO, ODBC, SPT, CursorAdapter, etc. For most day to day work, each method has pros and cons, and in the end, the differences were so small that it doesn't matter which you choose. I would not go with straight ADO, but would wrap it up in a CursorAdapter.
>>
>>>Hi,
>>>
>>>I am preparing for a meeting with a potential customer for a VFP/SQL Server 2008 application. I need to sound like I know what I am talking about <g>. I am sure one of the question they will ask is what driver(s) will be necessary to install on each client PC to use the VFP 9 application with SQL Server 2008. I have read various message where some suggest to use ADO, some SQL Server Native Client 10, or ODBC. What is the best or most efficient/recommended?
>>>
>>>TIA.