> If you know the SYSDBA password, you can do whatever you want. If you

don't

> know it, but have access to the database file(s), copy them to a machine
> with Firebird installed where you know the SYSDBA passord and you can do
> whatever you want. The only way to prevent anyone from fiddling is to deny
> them access to the physical database file(s). You can make it harder if

you

> encrypt the data and use illogical names for fields (e.g. call the
> customers table for parts or something - though this is more than likely

to

> confuse you as much as your customers), but the only thing you can prevent
> your users from seeing, is the code for stored procedures (you can delete
> the source code).

That's what I thought.

> A better way to avoid users fiddling with the system is to make it crystal
> clear that if they do so it is at their own risk. You take no
> responsibility for their changes whatsoever, and if you agree to run to
> their rescue when they prove their stupidity, you charge them far more

than

> you otherwise do.

I was thinking about distributing this on the web which makes this option a
little difficult.

> But the best you can do is to make such a great system that they don't

want

> to change anything, and be responsive when they want things changed.

If only people were satisfied with great systems.

Thanks for your help.

Regards,
Marcus.