>>>>The current series of drivers for SQL Server outside of Visual Studio are labelled "ODBC Driver xx for SQL Server". The are described as being compatible with all prior versions of SQL Server. We have had no problems with 11, 13, 15 and the current one, 17.
>>>>
>>>>They are also the drivers that are required for working with Always Encrypted on SQL Server, where the ODBC driver decrypts the data sent from the server.
>>>>
>>>>Hank
>>>>
>>>
>>>Hi Hank,
>>>
>>>Are you using VFP/SQL Server applications with SQL Pass thru? Are you using varchar(max) columns? Do you have any problems?
>>>
>>>Thanks in advance.
>>
>>Yes, Yes, and No (problems). When we have problems on a new server, it's 100% the case that old drivers (SQL Server, SQL Native Client) are the problem.
>>
>>Hank
>
>
>Hi Hank,
>
>When I ran a program supplied by Antonio in this thread, the only driver which I have installed and which didn't show the problem with varchar(max) column was SQL Server driver. I have ODBC Driver 13 showed C(0) for me.
>
>Did you apply anything extra for your VFP? I'm running VFP9 latest hotfix.

Come to think of it, I don't access memo fields using SPT. It can be done, but I can't find the reference (one of which supposedly exists on the UT). The other way is to use a cursoradapter, where you can mapvarchar or mapbinary as needed Because we a) generate all the "normal" views including ones parameterized on the PK and each one of the FK's and b) have some really complex views, we work with remote views, created in xCase, exported to SQL Server format and generated into remote views. We use SPT for quick queries that don't need an entire record.

Hank