>>Yes, I had this error regarding GUID casting to C(36). It seems to sometimes go wrong, especially with NO cursorschema.
>>
>>With varchar(max) I had the phenomenon it resulted in Char(0) fields (don't confuse with CHR(0)) if the first resultset record was an empty varchar(max). Varchar(max) works fine with the ODBC driver (Driver="SQL Server"), Ii get a memo field there in the resultcursor scheme, independant on the first resultset value in that field.
>>
>>So it seems with the SQL Native Client driver the automapping of varchar(max) fieldd to the vfp result cursor is working like vfp itself when determining the cursorstructure of resultsets with it's native sql on dbfs: Taking the scheme of the first result record. So maybe the bug regarding varchar(max) is by design. But the chr(0) issue in the conversion of uniqueid to c(36) could also be an error of SQL Native Client.
>>
>>Driver versions:
>>SQL Native Client: 2005.90.3042.00
>>SQL Server: 2000.85.1132.00
>>
>>All in all I second that for now the SQL Server driver is the safer option.
>>
>>Bye, Olaf.
>
>Yes, we definitely found that we were not seeing memo field data when using remote views against varchar(max) fields when we used the sql native client.
>
>Now always use SQL Server Driver in VFP apps.

Charles,
I'm using Native Client driver along with varchar(max), varbinary(max), guid and I don't have problems (maybe because that I use OLEDB).
Cetin