That's the boy. As I said, I never used OO4O in a completed project as it's benefits seem negible. It's benefits are:

a) Direct Access to Oracle Call Interface (whereas ADO uses OLE DB as an extra layer). Probably not going to make much of a performance difference
b) It's built for Oracle Stored Procedures. But I always found that ADO give me everythign I need
c) It's built for Oracle - say what you want about ADO being multi databse compatible - it was really built for SQL Server. However, again, you can usually do your work competantly enough using ADO & Oracle

However, ADO & OLEDB is used by almost everyone now, is asynchronous (OO4O isn't), and OLEDB is much quicker than ODBC....