Subject Re: problem with .Commit
Hi Helen,

Firstly, thanks for the quick reply. I'm happy to report that after
changing all twwIBOtable to tIBOTable, TIB_Database to TIBODatabase
and changing the properties you told me I can no longer reproduce the
problem (yet).

Thanks once again and apologies if I sound dumb :-)

--- In IBObjects@y..., Helen Borrie <helebor@d...> wrote:
> At 03:21 PM 18-10-01 +0000, you wrote:
> >Hi,
> >
> >After converting from BDE to Interbase I cannot get transactions
> >work despite trying out lots of stuff. Calling .Commit results in
> >Access Violation in ib_utils.
> What do you see in the callstack?
> What do you see in the SQL Trace?
> >I don't need multiple transactions
> >since I usually want this scenario:
> >
> >starttransaction
> >(lots of writes)
> >commit
> >and if an error undo EVERYTHING
> >
> >
> >Could it be one of my property settings?
> >
> >Autocommit = true;
> If you are using StartTransaction, then Autocommit will be
suspended. But if you don't plan to use Autocommit, make it False.
> >TIB_Database being used (with TwwIBOTables)
> TwwIBOTable is a descendant of TIBOTable. Use TIBODatabase. Also
make sure that the version of Infopower you are using actually needs
TwwIBOTable. The more recent distributions use TIBOTable.
> Check that your Keylinks are correct.
> >No Transaction components, using all defaults
> If changing to TIBOTable and TIBODatabase doesn't fix your problem,
do the traces and see what is being passed and report back with any
additional information.
> Also, show us the actual code snippets where you are starting,
testing and committing your transaction.
> regards,
> Helen
> All for Open and Open for All
> InterBase Developer Initiative ยท
> _______________________________________________________