>>>>>But couldn't you simply get the legacy ODBC and install it on your notebook that didn't have it?
>>>
>>>I could. What about the customer? My preference is the driver I'm sure will be there, meaning Native Client 11.
>>
>>How come I have many customers who buy computers all the time (Windows 10) and they all have the legacy ODBC driver. How come your customer does not have it?
>
>Hi Dmitry,
>
>I had a discussion started a month or two ago about problem with SQL Server ODBC driver. I forgot the details already, but hopefully you can search. We left this problem unresolved, I think.
I remember that discussion. And the result is that there is no perfect world. I know that legacy ODBC does not work with the Date type but works with VARCHAR(MAX). I can live without Date type (DateTime is ok by me). I think there is another type the legacy ODBC does not recognize but I don't remember.
"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
