buppcpp wrote:

> If the security db is nothing more than just another database, then
> why not added it's table's within the main database and get rid of the
> external security database?
>

There is no one right answer to the question "where do you put user
authentication data?" If you expect to have several databases that
participate in a single application, having a common location for
authentication data makes all the sense in the world. If different
databases serve different applications and different users, then each
database should have its own authentication data.

Vulcan allows the designer/administrator to choose the location for
authentication information - a named, shared database, local, or none.

Regards,


Ann