> Change your application install to ask for, if Firebird is already
> installed, the SYSDBA password. With it, create a new user, thaqt will own
> your database.

Sounds good to me. Very sensible.

> Im my modest opinion, you choose the rigth database, but a wrong approach

to

> it. But you just need to change a few things to make it happen.

Yes, you've engaged some very interesting thought patterns!!!

> Yes, you just failed in the installation approach. Instead of using

SYSDBA,

> thing about using a predefined user that will own your database. One
> friendly approach it's using some kind of prefix to your application to

your

> users, something like MYP_ARTUR, MYP_MARCUS, MYP_OWNER, etc.

I'm like what I'm reading.

> You must check for other workstation related problems also. Imagine that
> your users will use Interbase also, even just the client. You don't want

to

> mess around other configurations.

Is there a detailed document that goes into making a reliable installation?
I'm sure I've seen one somewhere.

> And yes, you still have security problems related to users can copy the
> database to other computer and look at your sp and triggers code. For me
> it's not a problem. There are always alternatives. Adapt yourself, and
> Firebird'it.

The SP and trigger code is going to be reasonably basic so they are welcome
to that. I've also come to the conclusion that if they want to mess about
with the database structure they can but the support will become null and
void and can only be re-instated for a costly fee. The data that is
sensitive will be encrypted.

Regards,
Marcus.