That said, SQL Native Client 11.0 supports ADO on the current SQL Versions, but only with a feature-set through SQL 2005. This is important to know when working with Unicode locales, where ADO is the only option for VFP working against SQL Server.

Rick Strahl's wwSQLAdo is a great tool to have when using ADO in VFP, FWIW.

>ODBC is the way to go. Microsoft has dropped support for OLE-DB (ADO) for SQL Server.
>
>
>>Hi all,
>>
>>A question relating to VFP acces to enterprise sql engines (Oracle, SQL server, Sybase, you name it). i have used the great client-server functionalities of VFP but that was essentially DURING THE PREVIOUS MILLENIUM:)
>>
>>I need to connect a vfp local decision-support application that is currently exclusively fed via local upload to server engines. What would be the recommendation in early 2016?
>>
>>The need ? Plain simple: A FAST (as fast as is possibly) way to download server data in the 10 or 100 of thousands records as read-only cursor stuff. I understand that ODBC is still a standard part of the MS-Windows standard install. Am I right? Is the ADO stuff still a solution or an alternative ? Would you recommend other solutions if any.
>>
>>Any input is welcome. I have not touched a db engine since 2004. An additional point: the use will be made in a plain vanilla corporate world of to-day.
>>
>>Daniel