>When you said about ver 10 and 11, "No data comes down and it comes down as a Character field", what you mean by that? I assume you mean the local cursor would be of type Character, but it will be empty? Ok, I could see that.

Yes, the local cursor will have a column with type of Character, but there will be no data if the SQL data type was varchar(MAX).


>Well, in my case, I upsized my data from the latest version of the Sedna Sql Server Upsizing Wizard (available from VFPX), and all of my memo fields were uploaded as Text fields in Sql Server, and when I run a SPT query from VFP using either ver 6 or ver 11, I do get data from the DB and it's a memo field.
>
>It doesn't appear that I have any varchar(MAX) fields in my DB, they all appear to be TEXT, and if not, I can certainly change them to be TEXT.

Right. Data type of Text works with all three drivers, I believe. It works for us as well. We made our Memo columns SQL Text data types.


>So, I am still at a loss for the pro or cons of ver 6 vs ver 11.
>
>Could there possibly be any performance issues? Also, I have a mix of Widows 7 and Window 8.1 and I'm sure that I'll have some Windows 10 online soon as well. (All 64 bit).

I wouldn't worry about the performance issues if there are any. But, you have to look at your data types in SQL and see which of them are or are not supported by the driver. The SQL Server 6 driver does not support Date or Datetime2 - unless you want to convert the character data it returns to be FoxPro Date and Datetime types.