Yes, and as long as Text is supported, don't worry. If Text is skipped at a later point, I will consider MySQL or another SQL server.

>Is the problem that you are using sqlexec()? Because otherwise, there should be no problem building it in. If you are using a wrapper for the sqlexec calls, you would have it instantiate your own cursoradapter class that automatically maps memofields (assuming you have the metadata for that available somewhere, which could even be the field name if you use hungarian notation).
>
>Hank
>
>>Unfortunately that's not an option for me, since I use my own framework.
>>
>>>Hi Tore,
>>>
>>>we use varchar(max) without a problem. We map types in the DBC (we use remote views). This can be done for cursoradapters as well (as one would expect, given that the same mechanisms are at work).
>>>
>>>Hank
>>>
>>>>>>Here's my experience...
>>>>>>
>>>>>>SQL Server (version 6):
>>>>>> 1. Will correctly read varchar(MAX) and the data will come down as a memo field.
>>>>>> 2. Will read Date and Datetime2 as character strings - not date types even though the data looks like a date.
>>>>>> 3. Will read smalldatetime and datetime as FoxPro type of T (datetime)
>>>>>>
>>>>>>SQL Native Client 10:
>>>>>> 1. Will *NOT* correctly read varchar(MAX). No data comes down and it comes down as a Character field.
>>>>>> 2. Will read Date and Datetime2 as date and datetime types
>>>>>> 3. Will read smalldatetime and datetime as FoxPro type of T (datetime)
>>>>>>
>>>>>>SQL Native Client 11:
>>>>>> 1. Will *NOT* correctly read varchar(MAX). No data comes down and it comes down as a Character field.
>>>>>> 2. Will read Date and Datetime2 as date and datetime types
>>>>>> 3. Will read smalldatetime and datetime as FoxPro type of T (datetime)
>>>>>>
>>>>>>
>>>>>>So, it's your pick of the poison.
>>>>>
>>>>>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.
>>>>>
>>>>>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.
>>>>>
>>>>>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 use version 11 without any problem. Only issue is that you must use Text instead of varchar(max). Officially Text fields are "not recommended for new design". This is what Microsoft has said many years now: "ntext, text, and image data types will be removed in a future version of Microsoft SQL Server. Avoid using these data types in new development work, and plan to modify applications that currently use them. Use nvarchar(max), varchar(max), and varbinary(max) instead." As I wrote, the first time I read this was many years ago, so I don't see the support for Text fields going away really soon.