I use the transaction object for that particular thread which is associated with the IBSQL. Why would it work with CommitRetaining but not Commit? I'll try what you said .... "Craig Stuntz [TeamB]" <craig_stuntz@nospam.please [a.k.a. acm.org]> wrote in message news:48934a9c$1@newsgroups.borland.com... Joe Sansalone wrote: try setting up the statement using IBSQL StartTransaction

If there are 3 different SQL updates within a transaction, and the first succeeds, the second fails and the 3rd succeeds ... will a Commit after the 3rd statement change the data to reflect SQL statements 1 and 3? "Craig Stuntz [TeamB]" <craig_stuntz@nospam.please [a.k.a. acm.org]> wrote in message news:489320f6$1@newsgroups.borland.com... Joe Sansalone wrote: So Commit really

Thanks Bill. I had a feeling rollback cases weren't taken care of. I assumed the code I inherited was based on good assumptions. I was wrong! Joe "Bill Todd [TeamB]" <no@no.com> wrote in message news:48925754$1@newsgroups.borland.com... Joe Sansalone wrote: What will the Commit within the finally do if the SQL updated something that another connection recently changed but

Thank you all for your help. Joe "Bill Todd [TeamB]" <no@no.com> wrote in message news:4890be06$1@newsgroups.borland.com... Vm|r Vlmez wrote: You should not commit after a select statement. Is this true or false ? It depends. It depends on when ? Connect a dbgrid to a datasource and also connect it to query, transaction and database. Okay now, execute a select and