> If the last number is invalid, then it will have to be changed.
> However, it would be very easy to fix even 1.0 and 1.5 to
> recognize that the next transaction id is going to cause
> problems, and set the database to be read only. I think that
> would prevent catastrophes...

Hello Ann,

That would be a very prudent change IMO. It would prevent the
fireworks (except the fact the database is no longer available to
'use' until it is backup-restored).

Obviously gfix would need to be modified to refuse to make such a
database writable with an informative error message (something like
'out of transaction IDs, you must backup then restore'), and a message
would also need to appear in Firebird.conf because it would not be the
first thing that came to mind when I could not start a new
non-read-only transaction. But to me this is preferable than having to
ask some third party to rescue my database by fudging the header pages.

Adam