>I have converted my BDE application that is using Firebird 1.5.3 to
>IBO4.6Bc. The application is running well, with some bugs that are
>being fixed as I run into them. I seem to occasionally run into a
>problem with a transaction holding up other transactions, and after
>the OAT does it's thing it will timeout the blockage and then work can
>proceed in that area of the program.

>I am interesting to tinkering with the timeouts, to shorten them so
>that if a transaction is blocked, it will terminate after a shorter
>period of time.

Jack, just a thought here before we all get carried away with timeout
properties...
you're talking about order creation... this involves using some existing
(commited) data and the insertion of new data.
I personally use a different model here completely... gather the existing
(unchangeable for this operation) data with a read only transaction (never
blocks), and use non-data-aware controls for the collection of the new (to
be inserted data). When the op wants to complete the order, they hit a
button,,, a transaction is started, field values are populated, and the
transacxtion is commited.. all in a split second.
Is this not possible in your scenarios?
Alan

>Any comments would be welcome to solve these two issues.

>Thanks In Advance

>Jack Engleman