Pete,

> I am not sure how to deal with the potential problems with SYSDBA
> and its default password. If I make my app change it, wont that
> potentially have an effect on someone else's program, or the
> database manager on the system my app is being installed on? Or is
> it fair to say that everyone else's app would create their own
> usernames/passwords anyway? So my app should just change the
> password for SYSDBA?

If any other application that uses Firebird is using its own usernames
and passwords they won't be able to create them without knowing the
SYSDBA password!

You should definitely create your database with your own user and not
with SYSDBA and try to connect with that user.

Store the real SYSDBA password somewhere in your database (encrypt it in
any way) so that you can connect as SYSDBA if you have to do special
tasks like creating a new user.
But take into account that these usernames might already be created by
the other app, too, which will make it impossible to create it!

If your users all use different usernames than your dbowner you have to
take care for the rights that are applied to your metadata.
Either you have to create a role for your uisers and grant the rights to
this role (and login with that role) or grant everything to public...

Luc.