This is what the Transactions Timeout properties are for.

There is a prompt and a force phase and you can set the timing for each of
these.

Jason Wharton

> -----Original Message-----
> From: IBObjects@yahoogroups.com [mailto:IBObjects@yahoogroups.com]On
> Behalf Of Rick Roen
> Sent: Thursday, January 05, 2006 5:59 PM
> To: IBObjects@yahoogroups.com
> Subject: [IBO] Re: open transaction
>
>
>
> > Transactions are not posted. DML statements are posted within a
> transaction.
>
> My mistake. I posted the TIB_Query which was attached to the
> TIB_Transaction.
>
> Here's what I wanted to achieve: The user posts a batch of new
> records via a TIB_Query. Then the TIB_Transaction is waiting to
> Commit. I want to notify the user that they need to commit if they
> wait too long, or take over eventually for their lack of attention.
>
> Do these settings operate under these circumstances, or should I
> just set a timer and prompt from that?
>
> Rick
> >
>
> > I'm not clear about what you want to achieve by this. You have
> the
> > transaction in WAIT resolution, which means that a DML statement
> request
> > could be hanging in an"unposted' state, waiting for another
> transaction to
> > finish. The application won't know whether the post is going to
> succeed or
> > fail until (or unless) it receives an exception. That can't
> happen until
> > the other transaction either commits or rolls back. TimeoutProps
> operate
> > on idle transactions. If your transaction is waiting for its
> request to be
> > executed then it's not idle.
> >
> > Helen