Oracle FAQ | Your Portal to the Oracle Knowledge Grid |
![]() |
![]() |
Home -> Community -> Usenet -> c.d.o.server -> Re: Oracle OLEDB driver and Schema Rowsets problem
I am sure for the MS OLEDB driver the syntax is correct. However, the
Oracle OLE objects (the Oracle oledb driver from Oracle) originally came out
before MS came out with any OLEDB (ADO) spec etc. It came out at least a
year before. So for the Oracle driver from Oracle the syntax looks wrong
because for the Oracle driver from Oracle it is wrong. If you look in
Oracle's online help file the syntax is more MS Access DAO like. They
(Oracle) have not changed it since then. I have used the Oracle OLEDB
driver from Oracle and it is quite good. It allows host variables and when
used properly is extremely efficient. If you have a requirement that you
cannot change the code (to go from one backend to another) and you must be
able to connect to SQL Server and Oracle then you will have to use the MS
stuff only.
Hope that clarifies,
Jim
"Alasdair Cunningham-Smith" <alasdaircs_at_metron.co.uk> wrote in message
news:972028593.25522.0.nnrp-03.d4f08801_at_news.demon.co.uk...
> Thanks for the reply, but this is straight ADO, and the sytax is correct
> because it compiles and runs OK in VB. Furthermore, it works correctly not
> only on both SQL Server 7.0 and 2000, but also on Oracle when using the
> Microsoft OLEDB driver. It only fails with a run-time error on Oracle with
> the Oracle OLEDB driver.
>
> Cheers,
>
> Alasdair Cunningham-Smith.
> MCSE MCSD MCDBA
>
> "Barbara Kennedy" <barbken_at_teleport.com> wrote in message
> news:zxOH5.13247$cO4.296068_at_nntp3.onemain.com...
> > If you are using Oracle's OLE objects the syntax is incorrect for that.
> > Look in the online help.
> > Jim
> > "Alasdair Cunningham-Smith" <alasdaircs_at_metron.co.uk> wrote in message
> > news:971968296.9399.0.nnrp-04.d4f08801_at_news.demon.co.uk...
> > > I have a VB6 SP3 application which talks to Oracle (8.0.5 and 8.1.5).
I
have
> > > both the MSDAORA and OraOLEDB.Oracle 8.1.6.2 OLEDB driver installed,
and
I
> > > can switch the code to use either.
> > >
> > > If I create an ADODB.Command with type = adStoredProcedure and
CommandText
=
> > > 'p_MEASITEM_i' and then issue com.Parameters.Refresh, it works with
MSDAORA,
> > > but OraOLEDB.Oracle 8.1.6.2 fails with error 0x80040e51 - Provider
cannot
> > > derive parameter information and SetParameterInfo has not been called.
> > >
> > > If I run the following code:
> > >
> > > Conn.OpenSchema(adSchemaProcedureParameters, Array(Empty, Empty,
> > > "p_MEASITEM_i", Empty))
> > >
> > > The MSDAORA driver returns a sensible rowset, but the OraOLEBD.Oracle
driver
> > > returns a rowset with the correct schema, but no rows.
> > >
> > > What am I doing wrong?
> > >
> > > Many thanks in advance for your time and attention,
> > >
> > > Alasdair Cunningham-Smith.
> > > MCSE MCSD MCDBA
> > >
> > >
> > >
> >
> >
>
>
Received on Sat Oct 21 2000 - 04:08:28 CDT
![]() |
![]() |