Hi!

Well, the problem is not so bad as you think.
I always use 'text' on the SQL server and it helps, query on it always return memo. However, when you have existing views, you will need to rebuild them after changing to text field type (or map type correctly in the properties of fields in view designer). This is needed to do not get error "the conversion required ...".
The article is right and mentioned by you thing is described in the VFP Help for data types conversion in following location:
Programmers guide, Chapter 21 (Implementing a Client/Server Application), near the end of this chapter contains paragraph "Controlling Data Type Conversion". See subnote for SQL_CHAR ODBC type. Type "text" on SQL Serevr is appropriate to SQL_BINARY in table there.

>Vlad, thanks for your help, but it's not as useful as We would like to be.
>
>If I use a memo field, VFP returns an error 1543 "the conversion required ...".
>
>There are an interesting article, "Comparing VFP and SQL Server 7.0 Datatypes" by Michael Levy in the MSDN Library that talk about this question.
>
>This article talks about something like that: I could try to set UseMemoSize property to something less than 254 and the data type to Char greater than the MemoSize. In this way, VFP will maps the field to Memo, but it doesn't work.
>
>I don't know if it could be a ODBC version problem.
>
>Kind regards.
>
>
>>Use memo field for this. You may map fields to any type using properties window for fields in view designer.
>> In addition, when you want automatically use memo fields, on the SQL server use 'text' field type to store text.
>>
>
>>>Hi,
>>>
>>>I´m trying to mapping an ntext field in SQL-Server 7.0 from VFP 6.0 Remote View, but I can't read and write more than 254 bytes.
>>>
>>>Can anybody help me?
>>>
>>>Thanks.