<?xml version="1.0" encoding="UTF-8" ?>
<?xml-stylesheet type="text/xsl" href="http://blogs.msdn.com/utility/FeedStylesheets/rss.xsl" media="screen"?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:slash="http://purl.org/rss/1.0/modules/slash/" xmlns:wfw="http://wellformedweb.org/CommentAPI/"><channel><title>ODBC Drivers Are Updated in Windows 7</title><link>http://blogs.msdn.com/buckwoody/archive/2009/07/08/odbc-drivers-are-updated-in-windows-7.aspx</link><description>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</description><dc:language>en-US</dc:language><generator>CommunityServer 2.1 SP1 (Build: 61025.2)</generator><item><title>re: ODBC Drivers Are Updated in Windows 7</title><link>http://blogs.msdn.com/buckwoody/archive/2009/07/08/odbc-drivers-are-updated-in-windows-7.aspx#9824688</link><pubDate>Wed, 08 Jul 2009 22:59:23 GMT</pubDate><guid isPermaLink="false">91d46819-8472-40ad-a661-2c78acb4018c:9824688</guid><dc:creator>bobb</dc:creator><description>&lt;p&gt;Hi Buck,&lt;/p&gt;
&lt;p&gt;This article is talking about a new ODBC driver manager, rather than new ODBC drivers. In fact it mentions that none of the existing ODBC drivers use these features and that there are no new ODBC drivers yet. &lt;/p&gt;
&lt;p&gt;Was the situation you refer to in SQL Server 6.5 caused by a new *driver* or new driver manager? Or did you actually have an ODBC-related problem with the new driver manager (I couldn't really read enough into the post to determine).&lt;/p&gt;
&lt;p&gt;I did see an old KB mentioning that there was a problem once that was caused by a new driver manager, but these are fewer than those reported against specific drivers.&lt;/p&gt;
&lt;p&gt;Cheers,&lt;/p&gt;
&lt;p&gt;Bob&lt;/p&gt;</description></item></channel></rss>