Helen, Adam,

>> Read only: yes. But !!! Read Committed for reports is terrible
>> !!! Reports should always use a snapshot transaction (Concurrency
>> isolation) to avoid getting discrepancies due to database state
>> changing during execution!

A> Amen!

Had you bothered to read the rest of the thread <g> you would have
known that the suggestion to make sure the read-only flag was set
stems from the necessity to help the old* transaction counters moving
forward, which was the subject of the discussion. To the best of my
knowledge Concurrency, which would otherwise be the first choice for a
report (and well-designed, disconnected interactive screens), doesn't
help in this case. BTW, not all reports are affected by the
discrepancy problems on Concurrency, and for some reports Concurrency
isn't even enough anyway. One assumes that if they worked with Read
Committed so far then it must be OK for the OP.

Ciao
--
Nando Dessena
======================================================
I support Firebird, I am a Firebird Foundation member!
Join today at http://www.firebirdsql.org/ff/foundation
======================================================