Re: SQLOLEDB vs. MSDASQL

• Previous message: Emmanuel LANDREAU: "Re: ConnectionString Without Password ?"
• In reply to: rpallares: "SQLOLEDB vs. MSDASQL"
• Messages sorted by: [ date ] [ thread ]

Date: Sat, 4 Sep 2004 09:37:37 +0000 (UTC)

rpallares (rpallares@discussions.microsoft.com) writes:
> We have a huge application in VB6 and SQL server 2k, I
> need to upgrade our version of ADO so that I can use it
> with SQLXML.
>
> Currently the provider for the DB connections is MSDASQL,
> can I change it to SQLOLEDB with virtually no impact on
> existing code that uses this and currently works with
> ADO2.5/2.7?
>
> Preliminary attempts have showed that won´t be straightforward. Which are
> issues? SQL Sintax? Recordset initialization.

SQL syntax should not be an issue.

There are situations where you are likely to encounter difference, although
many of them are subtle, like whether you get an diagnostic message or not.
Of course, even if the difference is subtle, it may still be important.

Since you mention XML, there is one case where there is an important
difference: if you have a query with FOR XML, you can retrieve that as a
regular recordset with MSDASQL. If you do the same with SQLOLEDB, you get
binary data instead. I believe you are supposed to use the Stream object
instead. Or, for that matter, SQLXMLOLEDB.

Overall, it would help if you detailed the problems you have had so far.

-- 
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp

• Previous message: Emmanuel LANDREAU: "Re: ConnectionString Without Password ?"
• In reply to: rpallares: "SQLOLEDB vs. MSDASQL"
• Messages sorted by: [ date ] [ thread ]