> The benefits of this is I get to use the table level security
> of permissions, trigger checks, etc. to control the security
> settings. Most importantly, I don't have to embed the SYSDBA
> password into the EXE of the program in any format whatsoever.
> It stays in a service process running on the server only.
> Totally isolated and secure.

Just in case you misunderstood. The approach I described (alterations
to the ISC4 database) does not require the SYSDBA password to be coded
or provided anywhere, not even in a service application on the server.

Still, I agree that service applications are very useful things. But
I still prefer my approach for user password management - for the
simplicity of its implementation.

Geoff Worboys
Telesis Computing