I agree they are different. I was incorrect in thinking that the VFP ODBC driver used the VFPOLEDB provider, as is apparently the case sometimes, but not here (as Craig pointed out).

>But it is still incorrect that VFPOLEDB is an ODBC driver:) It is an OLEDB provider. After 6 VFP didn't have an ODBC driver. I think you are mixing ADO with OLEDB provider. One is an application as the article says and other is an API accessing the data.
>In case of SQL server installations, it is just that they packed both the ODBC driver and OLEDB provider into same msi package. Still there are separate ODBC driver and OLEDB provider.
>Cetin
>
>>Correct, but it is what is used for ODBC connections. OleDB is what sits between ODBC and the database: http://www.4guysfromrolla.com/webtech/063099-1.shtml
>>
>>And as the article shows, DSNless connections can be made directly to the OleDB provider rather than the ODBC provider, with some provable benefit, even when hitting SQL Server. When you install SQL Server Native Client 10.0 OleDB provider, you will see an ODBC driver appear in the ODBC Manager driver tab. You can then access either the ODBC wrapper on OleDB, which is included in the SSNC10.0 install, or you can access the SQLOleDB driver directly.
>>
>>Hank
>>
>>>No it is not an ODBC driver.
>>>
>>>>While Dragan is technically correct, the VFPOleDB drives is also an ODBC driver. Any change you are using 64-bit OSs?
>>>>
>>>>>I installed VFPOLEDB but it's not in my data sources.
>>>>>
>>>>>When I look in the data sources in the configuration panel and in administration tools it's not there.
>>>>>
>>>>>Is there an additional step to put in the data sources?
>>>>>
>>>>>I have the same result on my desktop and my laptop.