Re: Returning resultsets with Oracle Stored procedures

David Russell wrote in message <01bcfce7$ab850e00$ab4195c1_at_thor>... <snip>
>This is all a bit messy, so why not use Oracle Objects for OLE, it is able
>to read out arguments from stored procedures that are of type : PL/SQL
>Table of Records.

IMHO using OLE is a bit messy, dangerous and slow. Messy because it makes distribution of software difficult as the OLE files (dll's and ocx's) must be included and correctly registered in the Windows Registry (ever tried to make any sense of the registration entries for OLE?). Dangerous as another application can quite easily install another version of the OLE object, and/or change the registration entries causing all kinds of problems in your application (I've seen it happened a lot). Slow because that's the nature of OLE - it loves CPU and memory resources.

I would think that any developer would like to know what's going on in his/her software. Using OLE is like a black box - you hope and pray the thing works ok, can handle multi-threading, does not cause GPFs in your application. etc. etc. Afterall, if anything happens in your app, it gets blamed by the user and not the underlaying OLE drivers.

I had a lot of problems with unreliable and shitty Oracle ODBC drivers - do you think that Oracle manage to code complex OLE objects any better than a simple ODBC driver? I would think twice before even considering to entertain a thought about thinking to including OLE in my applications. I'm not prepared to trust another vendor's drivers to enable my application to get the job done.

My 2'c worth. :-)

regards,
Billy Received on Mon Dec 01 1997 - 00:00:00 CST