Re: Oracle 8.0.5 and ADO 2.0 Question

In article <7fqel5$8rt_at_sjx-ixn9.ix.netcom.com>,   "Beth Massi" <bmassi_at_hmtreturn.com> wrote:
> Hi,
> Nobody posted any replies to the last post I made, so I thought I'd ask one
> more time. Guess not many people use ADO to access Oracle 8, huh?...
>
> I have a question regarding Oracle Version 8.0.5 and ADO 2.0.
> I am new to ADO and was under the impression that I was supposed to use the
> MSDAORA Provider when connecting to Oracle via ADO, however, when I try to
> open the connection it gives me an error message "Driver not capable". So I
> tried MSDASQL provider and it will let me connect, update, addnew recordsets
> and everything, which is great, but it won't let me create disconnected
> recordsets now. I get the error message "Operation is not allowed if the
> object is closed" if I try to do anything to my Client side recordset after
> disconnecting it (closing the connection). I am also concerned that the
> MSDASQL Provider will give me more trouble as I go on developing. Is there
> a version compatibility issue with MSDAORA Provider? Do I need to download a
> patch or something? or do I need to work with Oracle 7.3?
>
> Thanks in Advance!
> Beth

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."

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.

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.

Hope some of this might help you (and I really would recommend tracking that book down, too!)

-----------== Posted via Deja News, The Discussion Network ==---------- http://www.dejanews.com/ Search, Read, Discuss, or Start Your Own Received on Fri Apr 23 1999 - 16:35:31 CDT