Hi Selensky,

|Also, we have users that run complex reports and often leave the
|open on screen for hours.

When possible, read the records to memory and generate the report with data
from memory. This way you keep transactions short. Using something like
memory tables is a fast and easy way to acomplish this.

You can also use memory tables (or someyhing like an OPFs if you go
OO-style) in able to have shot WRITE transactions since you can "insert" all
information in memory and sent to FB only when finished -- but here, unlike
with reports, it *may* costs you some effort.


|The performance is OK at the moment, even with the big gap.

big gap and a recent restored db... it may get bad soon or latter


Regards,
Anderson