""Wilson, Fred"" <fred.wilson@...> wrote in message
news:E9E4431A916AD21191FD00104B986AEFC23879@......

> Mmmmmm, well, that does *not* appear to be the case (IB5.6).. I just

starte=

> d
> a restore (after dropping a database), and was able, with no problems, to
> log into the database (via WISQL) and do a select * from xxxx...

Maybe gbak was changed later because I can verify in code and in practice
that nobody apart from sysdba can log in while the db is being restored.

Was the db on a path with short names or not? I know a way you can log in
the same db twice and confuse the engine:
- userA creates db
- userB logs in before userA logs off (userA may be working with DDL or DML)
- engine sees two different connections.
This effect is the same if you replace userA by gbak.
I fixed that bug in FB but any IB still suffers from it.

C.
--
Claudio Valderrama C. - http://www.cvalde.com - http://www.firebirdSql.org
Independent developer
Owner of the Interbase® WebRing