Re: Oracle Ref Cursor and ADO do not play well together!!

"ericn" <ericn_at_sarek.cjb.net> schrieb im Newsbeitrag news:a271a1ed.0110311517.63cd0504_at_posting.google.com...

> I finally have resigned myself to the fact the ADO just doesn't work
> well with oracle.. it seems as if this might be yet another microsoft
> invention designed to break the competion's product

I think it would be reasonable to think about this problem from two sides. First, of course, it could be Microsoft with OLEDB and MDAC which are doing something wrong. Second, which seems to be forgotten, one has to regard that the OLEDB Data Provider (the database driver) has been created by Oracle. So it seems to be a very tough question, to decide whose fault it is.

There is absolutely no problem to return a recordset from a SQL Server via the SQL Server Data Provider. Some might argue, that this is the perfect prove for MS trying to break other's product. I don't believe in this for two reasons:

[1] Oracle did make this feature it work with their own provider. Obviously, as you wrote, there is some documented way for achieving this. Probably it is part of the Oracle OLEDB Provider's documentation (I did not look this up). Why should it work at Oracle's place and not at your place?

[2] If MS did code some contra-Oracle statements into OLEDB, wouldn't this be the perfect thing that could happen to Oracle? Then somebody would be able to *prove* and not just claim that MS is cheating at their competitors.

OLEDB is a based on a technology, whose interfaces are published. If you code something with regard to those interfaces and it does not work, publish it. If you find some contra-Oracle code inside OLEDB, tell Oracle about it. They will love to hear from you.

Michael G. Schneider Received on Fri Nov 02 2001 - 02:33:29 CST