Pros/Cons of ADO client-side cursors, Oracle 8i

Hello,

We have an Oracle VB application that uses ADO server-side cursors when connecting to Oracle (adUseServer). In order to speed-up a performance problem a client had with a batch module, we experimented with client-side cursors (adUseClient). It improved the performance of this module tremendously. We now have to try and choose the best way to incorporate this into our application without impacting other modules of the application. The original developer of our db layer interface put in a comment - something like "use Server side cursor to avoid ADO bugs with client side Oracle cursors". The developer is no longer available and I have no idea what kind-of bugs he encountered, or even what version of Oracle (may have been Oracle 7).

So, before we flip the switch to use client-side for our entire application, can anyone think of problems we may have if we do or don't? Note, again, it is Oracle 8i, using Microsoft's oledb for Oracle (MSDAORA).

Any helpful insights appreciated!

Julia Received on Mon Jan 12 2004 - 12:37:39 CST