>

As OAT was able to move forward and a
sweep did cure the problem, I guess there was either a largish
transaction, which was rolled back (and the engine wasn't able to
transform that into a commit).

Hi Thomas,

Thanks for the fast reply. So if I understand it well, it could be there was a large update running and the client killed the application through the task manager ? Or something like that.
I guess there is nothing much I can do about it ? But could that large gap between transactionnumbers be the reason of a performance drop ?
One more thing : is it a bad thing example : 10 users each of them several forms opened with lets say 20 readonly queries per user open. That's 10 users * 20 queries, results in 200 opened queries. Is that having influence on FB performance, knowing that these queries are all readonly. I guess the server has to keep a cursor open for each query ?

Thanks again !
Nico

[Non-text portions of this message have been removed]