> I certainly agree with your comment#3... I'm not looking to lock a user out
> of their own SQL Server totally (just when it comes to my apps).
> I simply wanted to know if SQL backends provided a secure means of blocking
> all users (dba's, consultants, end-users, etc.) from conjuring up a way to
> gain access to the database (assuming the user had full access to the server
> which held the database).

There is no way to block out the end-user from accessing the database
that is 100% secure.

Even if you encrypt the database you have to store the key somwhere,
the enduser has a chance to find the key and access the database.

This is an general problem and by no means specific to firebird. Foe
example on MS-Access the key for encrypting a database is held within
the database-DLL. Once this key is found the encryption is broken. The
same holds for the "password-management" which cannot be secure if all
parts of the system can be analyzed and modified.

> I am simply trying to confirm whether or not a secondary password or method
> now exists that truly locks all dba's and wannabe consultants from TOTALLY
> prying into an SQL database without the use of my application?

You can make this exist - but, you still have to hide the password in
a secure place and transfer it to the engine on a path the enduser
cannot grab it easyly.

Elmar