One of the first exposures I had to an ODBC driver was NOT a good one - the particular behavior for ANSI NULLS ended up causing some issues in a database application that I had inherited, so I tend to keep my eye on these things. Mind you, it was back in the SQL Server 6.5 days, and I haven't had an issue since then, but I keep an eye on it nonetheless.
Windows 7, which is set to release soon, includes a new ODBC driver - 3.80. It gives you several new enhancements which you can read about here, but keep this in mind when you're deploying a new operating system - this is exactly the situation that bit me. The point is, as always, whenever you make a change, test, test, test.