RDO, ODBC-Direct, and ADO fall short in some critical areas where VB
comes into the picture. One such important item is the ability to call
packaged stored procedures that return cursor refs. There is a laundry
list of others. OO4O is the way to go until Microsoft quits its
accidental? omission of critical Oracle interface features in its MDAC
specification. The drawback of OO4O is that the clients become
uncomfortably dependent on proprietary / nonstandard API's (namely
Oracle's OCI). It's a hard call to make universally.
Sybrand Bakker wrote:
>
> Hi Thava,
> You have three options:
> 1 ODBC (needs sqlnet). Not recommended if Oracle is the only database you
> are going to use
> 2 RDO in Visual Basic. Works for both sqlserver and Oracle. Probably needs
> sqlnet.
> 3 Oracle Objects for Ole, the Oracle implementation of RDO. Definitely needs
> sqlnet.
> Of course 3 is supposed to be the most efficient, while native.
>
> Hth,
>
> Sybrand Bakker, Oracle DBA
>
> Thava Arumugam <tarumuga_at_online.no> wrote in message
> news:ZeEj3.139$nz6.1331_at_news1.online.no...
> > We have an Oracle Database on Unix and want to use Visual Basic 5.0 to
> > produce some reports.
> > Is there any possiblities to use VB5.0 to connect to Oracle and if
> possible,
> > do we need both SQL*net and ODBC driver for Oracle.?
> >
> > Thanks in Advance.
> >
> > Brgds
> > Thava
> >
> >
Received on Sat Jul 17 1999 - 00:17:28 CDT
