At 10:15 AM 9/10/2004 +0000, you wrote:

>--- In IBObjects@yahoogroups.com, Helen Borrie <helebor@t...> wrote:
> > AlterUser(Action: TIB_AlterUserAction; AUserName, AUserPass,
>AGroupName,
> > AFirstName, AMiddleName, ALastName: string);
> >
> > Include uaModifyUser as your TIB_AlterUserAction argument and use a
>valid
> > user name in AUserName. Pass empty strings in the other arguments
>unless
> > they are used.
>
>Ah, this info about empty strings not being used is the missing info I
>needed. Thank you.
>
>Next question - how can I let a user change *their own* password?
>
>With TIBSecurityService, assuming I had granted permission as
>described at http://www.volny.cz/iprenosil/interbase/ip_ib_isc4.htm, I
>could simply follow the same process as if SYSDBA was changing their
>password.

Well, you're getting way off topic for IBO, but if you set up the view
named USERS, with the permissions and triggers as recommended by Ivan, and
it all works, IBO won't object. All users have read rights to the USERS
table, so your function to get the strings for the AlterUser arguments will
work for any user. When it comes to modifying users, e.g. changing the
password, it's the database that rejects unauthorised writes, not IBO.

Helen