Oracle FAQ Your Portal to the Oracle Knowledge Grid
HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US
 

Home -> Community -> Usenet -> c.d.o.server -> Re: Oracle 8.0.5 and ADO 2.0 Question

Re: Oracle 8.0.5 and ADO 2.0 Question

From: Carlos J. Quintero <cvivar_at_cat.es>
Date: Thu, 29 Apr 1999 11:43:10 +0200
Message-ID: <uJMZ2Sik#GA.273@cppssbbsa02.microsoft.com>

>I haven't really tried to use the MSDAORA native OLE-DB provider. I've
been
>using the MDSASQL OLE-DB Provider for ODBC. From what I've read, I think
>MSDASQL is the way to go, at least for the time being. This is what I've
>picked up from a book called "Oracle Programming with Visual Basic" by Nick
>Snowdon, which I highly recommend. It's very recent, too, and full of ADO
>stuff. Anyhow, Snowdon basically says that the early versions of the
MSDAORA
>have been really unstable. He kind of implies that the best strategy is
>"Wait until they get the bugs out of it before you think about using it for
>anything serious."

I have read that book and in fact only one chapter out of 18 is devoted to ADO. Most of the stuff can be obtained in the Microsoft documentation about ADO, but there are some things that are interesting.

>One thing he mentions that might be relevant to your MSDAORA situation (you
>can't open a connection at all, right?): the connection string syntax for
>MSDAORA is different from what you'd use for ODBC. Most notably, instead
of
>UID, you use User ID, and instead of PWD, Password.

You can also use the User ID and Password keywords with the MSDASQL + ODBC driver.

>As far as the MSDASQL side goes, I've had good luck so far using it with
>Microsoft's ODBC driver for Oracle. (Incidentally, the general consensus
>seems to be to use Microsoft's ODBC driver instead of the "Oracle" driver,
>which is actually put out by Intersolv. From my relatively brief
experience,
>I'd agree - the Intersolv driver seemed pretty flaky with ADO.) I haven't
>tried doing anything with disconnected recordsets, though, so I can't help
>you with that specific problem.

The book says that Oracle drivers are provided by Intersolv, but I am not sure of this. In fact, Intersolv has its own driver for Oracle which is by far the best ODBC driver available for Oracle. I am tired of reporting bugs of the Microsoft ODBC for Oracle driver which have been recognized as such by the tech support, but none of them is documented in the knowledge base. The same applies to the Oracle driver from Oracle corporation.

However, if you are using ADO, the best driver is Microsoft ODBC for Oracle because Microsoft only tests the MSDASQL + ODBC driver with its drivers. If some other driver operates in a legal manner according to the ODBC specification but different that the Microsoft driver, it probably will fail with ADO. The problem is that the ODBC API offers some freedom and the MSDASQL only accepts some ways.

Regards,

Carlos J. Quintero Vivar
Madrid (Spain)
cvivar_at_cat.es Received on Thu Apr 29 1999 - 04:43:10 CDT

Original text of this message

HOME | ASK QUESTION | ADD INFO | SEARCH | E-MAIL US