At 05:14 PM 14/12/2004 +1100, you wrote:

>NOW - this makes absolutely no difference when you think of just connecting
>to a database with a username and password. But when you wish to allow users
>the ablity to edit their own password and (most importantly) a SYSDBA to log
>on to your application, see a list of all users, edit/reset their passwords,
>delete users and also conveniently edit his/her own password... then you
>need the path to the security database.

Why? How would it be used where the (safer) alias would not? (Apart from
providing compatibility with InterBase, that is...but then, compatibility
with InterBase isn't quite what most people would view as a security
enhancement...)

./heLen