Thank you for clarification.
>Craig actually said connecting to *MS SqlServer* does not use OLEDB or ODBC - there's a native .NET provider for that.
>To clarify, other data sources (including VFP) may use the .NET OLEDB and ODBC providers which are essentially just wrappers around the original technologies.
>HTH,
>Viv
>
>>Thank you for clarifying. And if ADO.NET does not use neither ODBC no OLEDB, what is under the hood?
>>
>>>Let's clear this up. The preferred way to connect to SQL Server from .Net is .Net. If you use ADO.Net or Entity Framework you don't use either ODBC or OLEDB. Yes, OLEDB is being deprecated, but you still won't use ODBC from .Net.
>>>
>>>
>>>>The reason I was confused is somewhere recently I read (I believe here on UT) that Microsoft is deprecating the OleDb in place of ODBC when it comes to connecting to SQL Server. Of course, maybe I misread something.
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
