Thanks for your input.
I haven't used installers except for innosetup some time ago, but I
wasn't using firebird then.
My concern is to not destroy any other data they might have when using
the full server option.
And also, if they don't have firebird installed already, configuring
it. So basically the bad part there would be the SYSDBA password
setting I guess.
I'll check into doing my own custom-built installer.
Thanks for the idea.

>
> If you install everything, such as when using embedded, then you

know the

> default system user and password so you can use that to create the

owner you

> need for your database. If the server is already installed, you will

need to

> prompt the install user for the SYSDBA password. You can try the default
> first, just in case, but in most cases the password should have been

changed

> if the server has been running already.
>
> In my case, I have my own, custom-built installer that I use so

doing these

> things isn't a problem. It's all built in. If you use other

installers like

> Wise, etc., they usually have options for scripts/exes to run during or
> after install. Use that to set up the initial database stuff that

you need.

> Once the install program finishes, it can run an EXE that creates

the user

> needed, the new database, etc.. You can build a small app that does the
> work for you and run that after the install. Exactly how you do

things is up

> to the actual installer that you end up using.
>
> HTH
>
> Woody (TMW)