> Some advice please on handling transactions that stay open for
> prolonged periods (hours -> days).
>

Some days ago we experienced something alike.

We had a customer with so many sim. connections, that when people just
left they PC they held a long running transaction.

We solved this quickly by implementing a timer that after 30 min. of
inactivity just closed every open window, closing every open query,
committing every running transaction and exiting the program.

This solved almost every problem we have with transactions.
Before that the gab during a day could be as large as 300.000.
Today - It is seldom larger than 20.000 - 40.000 with 200+ connections.


I know that people says that I can just use a disconnected architecture.
This is a good idea, but it is not easely implemented. At least not in
our firm!

The timer part is easy - And works fine here.

Regards

Michael