Thanks Brandon.

I guess for me the important thing is that the DATE datatype works correctly since EVERYTHING we do has to do with multiple date fields. Fortunately for us, we don't do much at all or really nothing with TEXT or VARCHAR(MAX) fields.

>Jeff,
>
>I'm using the new date type in SQL Server 2008 and when I use SQLEXEC to pull a select * from a table I get the date field as a....
>
>If you use driver={SQL Server Native Client 10.0}
>the date field will come over as a date
>
>
>If you use driver={SQL Server}
>the date field will come over as a char
>
>
>Great! Because the {SQL Server Native Client 10.0} doesn't handle varchar(max) correctly, you have to use text fields instead.
>
>So in summary:
>driver={SQL Server Native Client 10.0}
>you get date fields correctly but can't use varchar(max)
>
>If you use driver={SQL Server}
>you get varchar(max) correctly but can use date's
>
>
>Hey, I have an idea... why doesn't Microsoft get off their ass and support their friggin product!