FYI: http://blogs.msdn.com/sqlnativeclient/archive/2006/09/27/774282.aspx
Here is a snippet from there : Must I upgrade clients to use SQL Native Client as soon as I upgrade my server? Applications deployed before SQL Server 2005 was released can and should continue to use MDAC. Applications must upgrade to take full advantage of the new features and data types introduced in SQL Server 2005 (http://msdn2.microsoft.com/en-us/library/ms131456.aspx ). When an application is upgraded, it should be thoroughly tested since there are some differences in behavior between MDAC and SQL Native Client (http://msdn2.microsoft.com/en-us/library/ms131035.aspx ). The vast majority of applications will not be affected by these changes, but this does not remove the responsibility to test before deployment. Jeff Jeff Johnson [EMAIL PROTECTED] SanDC, Inc. 623-582-0323 Fax 623-869-0675 Paul M¢Nett wrote: > Jeff Johnson wrote: >> Thanks Ted & Steve: I use connectionstrings.com but I needed to know if >> sqlstringconnect, etc. uses ODBC. Connectionstrings.com clearly shows >> that my connections use ODBC and I have informed my customer. > > SQLSTRINGCONNECT *does use* an ODBC driver, but *doesn't need to use* a DSN. > > Paul > > [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/[EMAIL PROTECTED] ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
