I stopped using this ODBC driver a long time ago.
It is created for SQL Server 2000. No TLS 1.2 support, no new fields types support.
Just install latest driver downloaded from Microsoft site.

>You are correct; this is SQL Server. Thank you.
>
>The 6.1 is on my PC and I have no problem.
>
>The problem this customer has (and it is just on one computer) is that the program sometimes stops working.
>
>The message the customer gets is as follows (comes from my VFP 9 application):
>

>SQL Server Error 17
>SQL Server does not exist or access denied.
>

>Another time she got the error:
>

>Driver is probably out of resources
>

>
>Note that the application starts. But then when she uses it, the error comes up. I have never seen these types of errors.
>
>
>>Hi!
>>
>>The SQL Server ODBC Driver could be responsible.
>>Which Driver do you use? 6.1.... This seems to be very very old.
>>We use the ODBC Driver 17 for SQL Server which Version number is 2017.178.01.01
>>
>>And: What are the Problems?
>>We've had problems with older Drivers with large Memo Fields.
>>Solution was always to use the newest Driver respectively the newest Driver regarding to the SQL Server Version.
>>
>>>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