>>Running a report, which just executes one large query, that returns many rows, seems to be fine. It's the opening of a screen that executes 5-10 queries to get various information from various places that seems to be the main problem. (changing the program to a single query isn't really viable)

>Make sure the report is not running in ReadCommitted isolation.

Reports (which ARE fast) run with the following transaction settings:

read
read_committed
rec_version
nowait

>>They are using Firebird classic FB 2.1.5 (and have been on 2.1.3 and 2.1.4 with the same issue)

>You have an unreleased snapshot on a production site????

Yup, these guys are also experiencing repeated index corruption and Vlad provided me with a patch to try (we ran it in house for 2 weeks first)

(The index corruption only ever happens in a very busy production environment at a handful of our largest sites)

Their slows downs were happening before the patch was applied.