Subject Re: database ballooning problem
Author Adam
--- In, "innoy1k" <duncan.chen@t...>
> Thank you very much of your advice, I must admit we have a bad
> database design here, because the process is relying on tables' state
> through out the codes, and a hard commit would change these states.
> Duncan

Why don't you try to use savepoint feature introduced with Firebird 1.5
rather than the IBO implementation. You don't need to commit until you
have completed your transactions work, and you can still rollback to
any previous save point in your transaction if required.