🚀 go-pugleaf

Nice to know I'm not alone!  I have a very different app setup but get
the same error.  Using an Oracle 8i server.

We have a lot of "support" functions that are usually passed a TADOQuery *
as
one of their parameters for general use.  Typically, they start:

int __fastcall MyFunc( TADOQuery * q, char * aValue )
{
    q->Close();
    q->SQL->Clear();
    q->SQL->Add( "SELECT blah blah" );
    q->Open();
    ...
    return SomeResult;
}

There are a LOT of these executed during operation, but only certain ones
throw the "Object was open" exception on the Open().  What's worse, it
will happen reliably at the same point when the app is run outside the BCB 5
IDE but won't occur at all when run in the IDE.

The place the error occurs can be found in include\atl\atldb.h.  Search
for DB_E_OBJECTOPEN Of course this only the template.  Any
ATL/OLEDB experts out there?

- Arnie


"Hans Martin Br�ckmann" <HMB@brueckmann-gmbh.de> wrote in message
news:3B714326.D1F6607F@brueckmann-gmbh.de...
> Hi there,
>
> I use MDAC 2.6 + SP and BCB 5.0 E with the latest SP�s. I have 2 unbound
> Master/Detail tables, which are controlled by InfoPowers 2000
> Comboboxes. The ADODataSets maste/detail  sync. is managed by a
> DataSource bound to the master and the detail�s SQL expression is
> parameterized. Everything is fine as long as I navigate through the
> comboboxes. But if I try to move to another record by calling
> tblDetail->Locate(....) and then again start to navigate the master
> table by accessing the combobox, the error "Object was open" occures.
> Afterwards the client table is closed. I reasured that when I move
> through the parameterized detail -table that i move insde the master
> given parameter value range. Even if I try to Locate a record which is
> out of this range, the Problem occures.
>
> I investigated this problem now for several days and did search the
> newsgroups but I didn't get any satisfying solution. Neither the client
> nor the master table�s ExecuteOptions are set to any of these
> async-switches. The tables are closed at design-time and opened at
> runtime. I am sure that this has nothing to do with infopower - it seems
> that it is an ADO problem.
>
> Thanks for help in advance
>