At 12:04 PM 9/05/2003 +0200, you wrote:

>Hello,
>I am using a TIB_Transaction in a peculiar way, e.g. to implement
>semaphores in my application through a semaphore table.
>
>To do this I am starting and committing the transaction explicitly,
>and trapping the deadlock exceptions. So far so good, but it appears
>that my open transaction is automatically closed after 120 seconds,
>which is the default setting for TimeoutProps.AllowCheckOAT.
>
>I thought explicit transactions would not be affected by OAT
>processing. The help says:
>
> > An explicit transaction is initiated by calling the StartTransaction
> > method. It will persist until one of the methods to end the unit of
> > work is called.
>
>So, does anyone think the help or the component is wrong in this
>regard, or it's just me?

A bit of all, probably. The description of the explicit transaction is
perfectly correct. The client application has to control the moment of its
completion.

>In the latter case, how can I setup a
>transaction that does not expire automatically?

Look at the other settings of TIB_TimeOutProps, especially ForceClosed. If
this is zero (the default) then the transaction will expire automatically
after two minutes of inactivity. AttemptTicks controls a duration you can
set to affect how long the overall task should be allowed before the OAT
checking kicks in.

You can also set it up so that it seeks confirmation from the user.

cheers,
Helen

(Fulda-bound, up to my ears in stuff to finish before the looooong flight
on Friday, so I'm going to be a bit quiet around here this week. :-))

---------------------
See you at the First European Firebird Conference May 19-20 in Fulda,
Germany
http://www.firebird-conference.com