Hi Helen,

Thanx for ua prompt reply

Just to clarify

>> I have set a database to read_only using gfix
>
> ******************************
>> and i also set on the readonly file attribute under the OS (windows).
>
> Why did you do that? Firebird database mode "read only" does NOT set
> the filesystem read-only attribute, nor does it intend that you should
> do that. A database that is locked inside a read-only file doesn't work
> - the engine has no way to write to the transaction inventory!

I am testing a database that ought to be distributed and permanently
reside on DVD hence setting the DB to read_only mode. As for the file
system, my take is that the database wount be readable while on dvd so it
should still function even with the readonly attribute set on.

In any case the DB works just fine and *is readable* both in readonly mode
and with the filesystem readonly attribute set to on. As long as am
issuing select statements only Firebird absolutely serves my purposes.

The exception crops up when i access any of the MON$* tables, even with a
mere select statement, but not with other tables. Once i access the MON$*
tables, new attachments to the database hang, and a detach from the
database with the current client also hangs


--
Using Opera's revolutionary e-mail client: http://www.opera.com/mail/