Re: DAO & Oracle stored proceddures

While I tend to agree. OO4O is not without it's pitfalls e.g. under 8.1.5, it can silently fail when fetching values from long columns.

And before anyone tells me to use blobs, I am, unfortunately, not able to modify the design of the Oracle system tables involved.

The way in which bind values are defined (last time I worked with it) on a per session basis is also a bit tacky.

"Sybrand Bakker" <postbus_at_sybrandb.demon.nl> wrote in message news:paj04u4m5vr0o4lkte2l07e5op9r8dck45_at_4ax.com...
> On Sat, 12 Jan 2002 11:11:15 -0000, "Robert A.M. van Lopik"
> <lopik_at_mail.telepac.pt> wrote:
>
> >Soory Peter, but I don't agree. DAO (data access objects) together with
RDO
> >(remote data objects) together are the predecessor of ADO. Through ODBC
they
> >are perfectly able to talk to Oracle.
> >
> >cheers
> >rob van lopik
> >
> >
>
> Anyone needing access from VB to Oracle should avoid ODBC like *hell*,
> as Oracle ships Oracle Objects for OLE with every client, with
> interfaces to VB and Visual C++. OO4O is a *native* driver, which
> doesn't suffer from the pitfalls and quircks of ODBC.
> OO4O also comes with sample code.
>
> Hth
>
>
> Sybrand Bakker, Senior Oracle DBA
>
> To reply remove -verwijderdit from my e-mail address
Received on Sat Jan 12 2002 - 13:23:50 CST