This has the same "flavor" as writing DAO code. However, it is much faster
than ODBC based apps. There are two reasons for this, the first is that it
communicates with the Oracle Call Interface (OCI) layer directly instead of
going through ODBC to it, the second is that it is optimized for Oracle,
whereas ODBC is not. Also note that Oracle only directly supports forward
cursors in ODBC, however with oo4o, you get bidirectional capabilities. The
downside is that you lose the flexibility to switch databases that ODBC
gives.
Rick
Peter Hiemenz wrote in message ...
>In article <7hs14v$97u$1_at_weber.a2000.nl>, Arjan van Bentem wrote:
>> You may also use Oracle Objects for OLE (oo4o) in your VBA code.
>>
>Is this working well? I just removed using the ODBC driver supplied
>with the 8.0.3 client and replaced it with the current MS one.
>
>Peter Hiemenz
>Hilden
>Germany
>
>PeterHiemenz_at_compuserve.com
>
Received on Tue May 18 1999 - 23:48:47 CDT
