>>As Jorge points out, the ODBC Driver XX for Sql Server series works well. (11, 13, 15, 17)
>>
>>We have been using this series at multiple customer sites since 11 was released many years ago.
>>
>>Microsoft guarantees that all drivers in this series will be compatible with prior drivers in the series.
>>
>>There is no reason to stay with outdated drivers, and as has been pointed out in this thread, there is risk associated with staying with older drivers.
>
>Actually, that's not true. As I wrote in another reply, some of the drivers supports memo fields, and some of them support datetime (or is it date), but none of them supports both. I confess that I may remember wrong about which field types are supported, and which are not. I believe that varchar fields are also affected.
>
>>Hank
>>
>>>Hi,
>>>
>>>My VFP 9 application connects to the SQL Server via ODBC driver. The application can get the ODBC driver version.
>>>One customer has a problem with the application. And it seems (not sure though) that the problem is with the ODBC driver.
>>>Their ODBC driver version is 10.0.18362. My PC has ODBC driver and the version is 6.1.7601.17514.
>>>
>>>Is 6.1 older version than 10.0?
>>>
>>>TIA

Hi Tore,

We haven't had a problem with datetime fields in any version less than 10 years old from today. I have a vague memory of there being an issue with the old default SQL Server driver, but memory that far back is hazy. Heck, get old enough and most memories are hazy -- there are so many.

For memofields, we have generated the SQL DB from our VFP app metadata as varchar(Max) from long before the ODBC Driver series, so we never ran into an issue.

Hank