>>Hi,
>>
>>I wanted to test the VARCHAR(MAX) type with SPT approach in VFP 9. I added a test field to one of the tables, type, VARCHAR(MAX). Then on a form I added an EDIT BOX and bound it to the cursor created by calling the SQL Server with SPT. Then I edited the entry in this edit box and saved it. Everything works. I close the app and reopened it again and the value I typed is in the field.
>>
>>So I suppose even though VARCHAR(MAX) is not 100% compatible with the ODBC it works on saving the data, correct? I am just trying to see if I can use VARCHAR(MAX) instead of TEXT and get away with it.
>
>Try the same thing except with a DATE field instead - it will come back as a char field instead of a date. Now if you switch to the new version of the driver you'll find that VARCHAR(MAX) comes back as a char(0) field, but the DATE field comes back correctly. Really irritating. The old version of the driver works for some things, the new version works for others.

First, thank you for explaining it. This really makes me mad at MS. Couldn't they (with all their money and power) combine the earlier version feature into the latest version of the driver!? I want to use some stronger words towards MS but don't want to be banned from UT.