All,

This is a follow up to the a thread that already exists, the "Firdbird
Deployment".

In summary I want to write an application that is downloadable from the web.
When the user installs the app it will also install firebird if not already
installed.

I have two main questions.

1. If the installation program installs Firebird then the application can
take control over the username and password. However if the user wants to
use Firebird for their own development, they wont have to install Firebird
but they wont be able to use it either. Because I would have setup Firebird
on that machine with my own SYSDBA username and password.

2. If Firebird is already installed and the user has their Firebird server
setup in such a way that none SYSDBA users cannot add users, I'm screwed.

Thinking about this I don't think I've chosen the correct database. I think
Firebird is more for Client/Server applications, where as I'm after (for
now) a single client database that is secure. Does anyone else agree?

I was hoping to use Firebird for this as for the first release of my app it
will be a single app deployment. However as the application grows (and I
hope it will) its possible I will move into the realms of Client/Server. I
have so far designed it to be as Client/Server friendly as I know how.

Regards,
Marcus.