Milan wrote:

> LOL it's longer than I thought so I don't remember it exactly. I did the
> trick with adding SYSDBA role (using insert command into RDB$ROLES) and
> I'm pretty sure that I added this role into RDB$ROLES into security
> database.

Oh, that's surely possible. After all, the security database is just a
database, so you can define roles in it. But those roles only affect the
security database itself, not other databases.

If you define a role in MyDatabse.fdb, all the information about that role
is stored in Mydatabase.fdb; the security database doesn't even know about
its existence.


Cheers,
Paul Vinkenoog