>>>>What do you mean by queries against VARCHAR(max)? I use this type of column and SQL Select from my VFP SP2 application with WHERE clause. What am I missing?
>>
>>Are you using the classic SQL Server ODBC driver? The classic driver predates VARCHAR and fortuitously gets VARCHAR(max) right but has other issues. Newer Native Client drivers on many Windows installs, return a C(0).
>
>Yes, I am using the SQL Server ODBC driver. I will keep in mind not to have the customers update to the Native Client because I have not found any issues with the ODBC driver.

I have written about the ODBC driver business a couple of times. I don't have the ability to re-evaluate it, but what I found out is that:

1. I believe the SQL Server ODBC driver will see varchar(max), but will not see Date or DateTime2.
2. I believe that the newer drivers see Date and DateTime2, but see varchar(max) as char(0).

I forgot where SmallDateTime fits in, because I avoid using that.

However, I do like to use Date and DateTime2.

So, really varchar(max) is a big problem if you want to use Date or DateTime2. I controlled our SQL Server database and forced all the varchars over 8000 (I think that's the number) or varchar(max) to be SQL Text columns. But, MS is threatening to pull support for the Text column.