Here's my experience...

SQL Server (version 6):
1. Will correctly read varchar(MAX) and the data will come down as a memo field.
2. Will read Date and Datetime2 as character strings - not date types even though the data looks like a date.
3. Will read smalldatetime and datetime as FoxPro type of T (datetime)

SQL Native Client 10:
1. Will *NOT* correctly read varchar(MAX). No data comes down and it comes down as a Character field.
2. Will read Date and Datetime2 as date and datetime types
3. Will read smalldatetime and datetime as FoxPro type of T (datetime)

SQL Native Client 11:
1. Will *NOT* correctly read varchar(MAX). No data comes down and it comes down as a Character field.
2. Will read Date and Datetime2 as date and datetime types
3. Will read smalldatetime and datetime as FoxPro type of T (datetime)


So, it's your pick of the poison.