Thanks Alan, can I ask a few questions on what you said...

What program would I use to take the backup and create a new copy of the
database with the new owner?

Secondly, the type of person that will be downloading and using my
application will be non-technical. To them, they will install Firebird and
that is all I want them to have to do before they can start using the
application. They might not even know what Firebird is, just they need it to
use the app. Can I not create the owner user of my database in my Delphi
application?

"deploy with embedded only" - can you explain more what you mean? I take it
you mean the embedded version of Firebird. How does that work?

Thanks,
Stephen

----- Original Message -----
From: "Alan McDonald" <alan@...>
To: <firebird-support@yahoogroups.com>
Sent: Friday, August 15, 2008 1:43 PM
Subject: RE: [firebird-support] Firebird sysdba account

> the easiest way with your situation is to take a meta data backup and
> create
> a new database with the name of the new owner (a new/separate user).
> Then insert the data as this or another user.
>
> You need user management as part of your application (I suggest). GSEC is
> pretty ordinary for an application. most component sets have a services
> manager/security component. The first thing after installing to a new
> server, the appointed SYSDBA (the person who installs the server and has
> to
> know what the SYSDAB password is) has to create this DB owner user and
> provide it a password.
> Then this admin person needs to create additional users.
> This person has to either grant roles to these users or give the owner
> password to a person who administers the application (not the server), so
> the new users (created by SYSDBA) can be granted the appropriate roles to
> access the database by the owner user.
> Therein lies the hierarchical nature of granting permissions. Someone at
> the
> client, since they own the hardware that FB resides on, must have the
> right
> to have the SYSDBA password. And so they have the right to provide
> permissions down the line of administrators and users.
>
> If you choose to deploy with embedded only, then no such user management
> is
> required.
> Alan