Hi Jeff,

>>I did one simple update back to SQL Server's varchar(max) column. It worked, but you never know over the long term whether it works. Interesting.

/edit/

RV and CA effectively sit on top of SPT so I just checked that you'll see the C(0) if you create a new VFP9 RV or CA with one of the newer drivers and don't fix it with cursorschema for CA or field definition for RV. I can't provoke the NULL error today, though.

I suspect that existing CA created with the old driver will have Varchar(max) mapped to Memo in the cursorschema, so may continue to work. However, the CA builder throws errors with newer drivers if your Select includes a VARCHAR(MAX) field and I have not tested what happens if you mess with an existing CA, since VFPA gets it right by default- not just for Varchar(max) but also for Varbinary(max) and XML field types.

FWIW I also seem to recall a SPT work around using CAST, but (sounding like a stuck record!) VFPA makes these workarounds obsolete.