Hi,

> My point is that if the user knows the SYSDBA password then they can see
> everything. If they don't know the password they can setup a separate
> interbase server where they know the SYSDBA password and access the database
> from that server as SYSDBA. OR am I missing what you are saying. Can I
> actually setup permissions in such a away that not even the SYSDBA can
> access the data?

The database file is supposed to reside on the same server as IB/FB is
installed. So, in order to copy the database, the user has to have
access rights to the physical file of the database, which the user
doesn't need.

> This brings me onto my next topic of conversation (which I'll start a new
> thread for as I can see it being quite topical), deployment to a machine
> where interbase is already installed.

If Interbase is already installed, then there's nothing you can do
about the SYSDBA user. That might be up to the system administrator
to set things up properly.

Daniel Rail
Senior System Engineer
ACCRA Group Inc. (www.accra.ca)
ACCRA Med Software Inc. (www.accramed.ca)