Hi,

Yes. Thanks for that. I had come to the same conclusion after reading all of the thread that you had referenced. It looks like that there was some hope that there would be a SP that would fix this, but I guess it is not very likely now.

Unfortunately, ADO is not really an easy option for us so I guess we will have to make a choice of either

"DRIVER={SQL Server Native Client 10.0};" which supports the new SQL Server 'DATE' type. but not XML or the NVARCHAR(MAX) datatype. OR
"DRIVER={SQL Server};" which supports XML and NVARCHAR(MAX) as memos but not the new DATE type.

Thanks for you help in identifying our options. Definitely worth 3 stars I think.

Regards

Mace


>VFP doesn't know anything about new SQL Server data types and cannot interpret them correctly with new ODBC drivers. A workaround is to use CA with ADO.
>
>
>>
>>We are actually using the driver "DRIVER={SQL Server Native Client 10.0};", but I decided to take a look to see what the impact would be if I used the legacy driver "DRIVER={SQL Server};".
>>
>>What I noticed is that we get the XML datatype in a Memo using the legacy driver, but not with the Native Client 10 driver. It is the same thing when using VARCHAR Max. Also we can't use the old legacy driver as this would mean that we could not use the SQL Server 'Date' Datatype.
>>
>>Very strange.
>>