<SNIP>

> If everyone follow the rules for client/server deployment, you shouldn't
> have any problems deploying your application: just ask for the sysdba
> password and you're ready to go.

One thing you have to realize that most developers in this market space (small
custom apps) don't follow the rules.

Most of us have switched to IB/FB from some other desktop or client/server
database becasue of the power and ease of deployment. As far as I see it, FB has
a great potential to succeed in this space, but deployment problems like this
need to be soon before FB gets a bad rap..

Currently I am working on convincing my company to switch from MSDE to FB as a
backend for one of our products. Expected deployments: 20.000, expected number
of clients 1-25 per deployemnt. Our customers have no clue what ctrl-alt-del is
let allone what the SYSDBA password would be. As you can imagine, if we don't
play nice and nuke somebodys FB install in order to install our application, we
will make a lot of unahppy developers :-) On the other hand if we dont do it
then we shoot ourselfs in the foot, bacause the customer won't be able to use
our software and will switch to the competition. (and guess what a for-profit
company will do :-)?)

> That's what we get from easier deployment: people using Firebird as if
> it was is own server.

Let's consider this:

well, yes you were the first one to install FB on this computer, but you also
changed the SYSDBA password. You did tell the user the new password, but he
forgot it as quickly as he clicked OK on that message box. Now what? The only
thing I can do is to kill your security.fdb and hope that the customer needs my
software more then he needs yours.

Is there a sollution to this problem? I don't know, maybe the security should be
tied to teh database files and not the server, maybe there are other solutions
but one thing is for sure: a lot of people are in the same boat as Thomas and
are getting really nervous as more and more developers flock to FB.

Raf