The problem is that when the aPtrRecordset object is deleted, there is a memory exception. If I remove the delete, VC++ tells me that there is a memory leak.
Everything else in the class works well (queries, calling stored procs, etc...)
The same kind of memory error occurs in code like this:
for( int index = 0; index < fieldCount; index++ )
OField field = fields.GetField( index );
// do something with field
When the OField object is deleted at the end of the for loop, there is a memory error.
When I follow the code in the disassembly window, the error seems to be in the Oracle object destructor.
Is there something specific to do when using OO4O in a DLL?
Is it because the DbOo4OClass instance is created in the application context and OO4O calls done in the DLL context?