There is no security if the mdw file can be seen by users

[gazelle04]

I've been searching for an effective way of security an Access database. From creating database password, encrypting, disabling shift key at start up, and the user-level security.

The user level security is the most secured way of protecting Access database. But if the mdw file will be distributed or will be known to users then security is gone by just paying for password cracker software easily available in the internet. They can also crack database passwords. These softwares are easily available for just 20 US$.

I've been reading from the internet that to distribute your user level security enhanced database you need to also distribute the workgroup information file (*.mdw) file. Otherwise they cannot use your database.

[puppydogbuddy]

I've been searching for an effective way of security an Access database. From creating database password, encrypting, disabling shift key at start up, and the user-level security.

The user level security is the most secured way of protecting Access database. But if the mdw file will be distributed or will be known to users then security is gone by just paying for password cracker software easily available in the internet. They can also crack database passwords. These softwares are easily available for just 20 US$.

I've been reading from the internet that to distribute your user level security enhanced database you need to also distribute the workgroup information file (*.mdw) file. Otherwise they cannot use your database.

Yes. See this link: http://support.microsoft.com/kb/305542
Remember, application security is in addition to windows authentication, and after you have converted your mdb to an mde file, effectively removing the source code to your database. Unless your data or database design is so extraordinarily valuable or sensitive, I don't think anyone is going to go to all that trouble (assuming they have the technical skills to do it).

[missinglinq]

What's being secured from whom has to be the cardinal question, when dealing with security issues.

If you have toddlers about the house and you don't want them messing around with the computer in your home office, you put a child-proof cap on the door handle.

If you frequently give parties and don't want your guests wandering in to the same office, you replace the door knob with one that open with a key.

If your home office is the storage facility for the secret Coca Cola formula, worth millions, you add a biometric access system, pressure pads, armed guards and dog patrols.

You get the idea.

Looking at a database, the questions become are you trying to protect your data, the integrity of the structure of your database, or both, and from whom?

If you're trying to protect data and or the structure (design) of your db from casual snoopers, i.e. authorized users with too much time on their hands, a combination of user level security and/or conversion to MDE files will do the trick. The same applies if you simply don't want the janitor, working after hours, accessing a copy of your customer list.

If, on the other hand, you're worried about a high level techie coming in with the sole intention of stealing proprietary data, then you need to be using something more than just a plain Access database. MySQL and Oracle can be used as the back end for an Access front end and provide a great deal more in the way of data security.

And in the final analysis, any security system that can be implemented by man can be broken by man.

Linq ;0)>