Alan,

> > >> Via the Services API or "gsec".
> > >>
> > >> Not via SQL.
> > >>
> > >> Martijn Tonies
> > >
> > >Quoting from release notes: "The SYSDBA remains the keeper of the
> > >security database but users can now modify their own passwords by way
> > >of a view over the (new) underlying, protected RDB$USERS table."
> > >
> > >Seems to me there is a way to change it via view ... real-life example
> > >would help greatly.
> >
> > Then try it. You cannot connect to the security database, it is
> > prohibited.
> >
>
> what annoys me a little is that DBOwners cannot use GUI tools to grant
> objects to users, since gui tools rely on DBOwners being logged onto the
> database and once logged on, other users are not visible (in the GUI

tools).

> Only SYSDBA will see a full list of users.. So the only way this is

possible

> is to modify security2.fdb so the view reads
> ...
> WHERE CURRENT_USER = 'SYSDBA'
> OR CURRENT_USER = RDB$USERS.RDB$USER_NAME
> OR CURRENT_USER = 'MYDBOWNER'
> ... OR (keep adding database owners)...;
>
> Then you get the GUI grant manager tools working for the database which

has

> been created by MYDBOWNER.

The list of users is probably fetched by using the Services API.

What do you propose as a solution?

Martijn Tonies
Database Workbench - tool for InterBase, Firebird, MySQL, NexusDB, Oracle &
MS SQL Server
Upscene Productions
http://www.upscene.com
My thoughts:
http://blog.upscene.com/martijn/
Database development questions? Check the forum!
http://www.databasedevelopmentforum.com