I have only just picked up on this so I may be a bit off track.

User configuration on Interbase is a bit of a mess. This is not a IBO
problem
but Interbase itself.

The table of users is managed by the Server ( and we have to duplicate
that
across a number of machines to keep the user table in sync ), while the
level
of access can be controlled within the actual database.

If 'Nando' does not exist in the table of users on a particular Server
then they
can not access any database on that Server. If they do, then the level
of control
within each database is very good. If they do not have 'DELETE'
privileges then
the Server sends an error message, which IBO can then handle as
required.

I started with IB5, so I have not got around ROLES yet, which is
supposed to
make assiging a particular set of privileges to a group of people
easier.
We use PUBLIC for INSERT and UPDATE, but restrict DELETE to SYSDBA and
it
works fine. The only additional coding is to pick up the 'no permission
to
delete message' and give the correct user massage.

--
Lester Caine
-----------------------------
L.S.Caine Electronic Services