Thanks, Craig, but that did not help. I've googled a lot on this and see that varchar(max) simply doesn't work, not only for FoxPro, but other things as well and MS doesn't seem to be doing anything to change that based on the dates of the posts I've seen.

Ok, I might have to change my varchar(MAX) to old and soon to be deprecated Text fields in SQL. Really don't want to do that!

But, what is puzzling me is why the regular less than 254 character varchars are coming done as plain Chars.

Maybe the varchar(MAX) is poisoning the well?

>It works, but you have to be aware of what you can and can't do. This may help http://www.tek-tips.com/viewthread.cfm?qid=1642816
>
>>I'm using this as a connection string to a SQL 2012 Server:
>>
>>?sqlstringconnect("Driver={SQL Server Native Client 11.0};Server=dev;Database=foobar;Trusted_Connection=yes;")
>>
>>Unfortunately, my SQL 2012 table has varchars and they're all coming down to VFP9 as plain old chars and the varchar(MAX) is coming down as Char(0).
>>
>>At least the Date is coming down as a VFP date.
>>
>>Is there a better ODBC driver to SQL?
>>Am I in trouble for using varchar(MAX)?
>>Am I in trouble for using SQL 2012?
>>
>>TIA