> Sorry,
>
> Firebird 1.5 running on Windows 2000 Server. I restored the database
> along with several other databases and 1 database is now producing the
> error I listed. No, forced writes is NOT on.
>

windows - should always have forced writes set to ON.
If you can backup restore again after you have followed Paul Beach's steps,
you may get rid of it.
If all this fails, and I assume that the db is useable? when do you get this
error? on connection? at some other time?
if it's readable, it might be just as well to create another shell from the
extracted metadata, and pump the data across to it.
Alan