Subject to protect or not to protect?
Author Piotr L

I'm working on an application that should be delivered to the client
with Firebird database.
I'm curious what options exist for me for database protection.
Should I protect anyway my database from out-of-application access?
I would call it rather a "design" problem.

As far as I know it is impossible with Interbase / Firebird,
because passwords are specified for the serwer, not for database.
To put it in other words, should I even try to protect this data
stored inside the client database?
Or should I give user name & password to
the administrator and forget about the whole thing?

How other developers are doing this for shareware-class applications?