>>Yes casting works and also if you use ADO instead of ODBC you don't need any casting.

If I use ODBC ( the one that isn't sql native client ) when I create the ODBC connection, everything works without casting. But SQL Native Client seems to either have a bug or an 'undocumented feature' <s>

So this is known behavior of SPT and varchar(max) and SQL Native Client?

Is it documented or mentioned anywhere? Sure made me crazy trying to figure out why some my views worked and some didn't in retrieving memo data.



>>Does anyone know how to get varchar(max) fields to return data into a memo field using SPT and the SQL Native Client?
>>
>>Our framework has two ways of implementing remote views. If we just open the remote view as it is written a M field mapped to VARCHAR(MAX) returns data as expected. If we use SPT on the same view select ( we build it on the fly to implement dynamic view parameters from DBCX ), the memo fields are empty as if fetchmemo were false ( it isn't )
>>
>>This is using SQL Native Client for the driver.
>>
>>In the same scenario if the connection uses the ODBC driver, the memo data comes in with either method as it should.
>>
>>I guess I should not be surprised that in the wonderful world of Microsoft only the older driver works properly with the newer data type <g> but I thought there may be some trick in SPT using SQL Native Client to get this to work properly.
>>
>>FWIW casting the varchar(max) in the remote view works with SQL Native Client
>>
>>cast(testbed.mnotes as varchar(1000)) as mnotes
>>
>>
>>
>>TIA
>
>Charles,
>Yes casting works and also if you use ADO instead of ODBC you don't need any casting.
>Cetin