Re: Protecting an Access Database

"Scott McDaniel" wrote:
Nando wrote:
Any ideas on what to do to better protect the database after using ULS? I
don't know what those unlockers do. Do those programs crack the Admin
password? Curious, because I want to make my database more secure.
Sometimes
db users (employees) have too much time on their hands.

The password crackers give you a list of all users in the database, along
with their passwords. Once you have this
information, it's easy to log in as an Admin user and do what you want.

ULS is about as secure as you can get with Access/Jet. If you need better
data security, you'll need to move to a
different database engine like SQL Server, MySQL, etc. Note that SQL
Server Express is free and is generally more secure
than Jet - although that's not always the case.

Thanks Scott! I see...So I guess that not even encryption (which I have not
used yet) would have made the MDBs more secure.


.

Relevant Pages

  • Re: Access Security not secure
    ... You should secure it manually. ... > In your test with using a new workgroup and running the> wizard it was in access2000 then again in access2002 ... >>> to work well until I try to access the database on the ... >>>>> I created the Administrator and added him to the> admin ...
    (microsoft.public.access.security)
  • Re: Problems setting up access security
    ... The Admin user still owns the database object. ... You secured it using the system.mdw, thinking that you were using your secure mdw. ...
    (microsoft.public.access.security)
  • Re: is Admin a kinda of a genius?
    ... While you can't delete the Admin user, when you secure a database, you're ... > different wrkgrp file. ...
    (microsoft.public.access.security)
  • Re: Access Security not secure
    ... The first step is to create a new workgroup. ... > I created the Administrator and added him to the admin ... > No luck if I try to open the database from a computer that> is attached to the default workgroup I have full access to> the entire database. ... >>Should secure your database enough. ...
    (microsoft.public.access.security)
  • Re: is it possible to make a database secure after creating it as unsecure?
    ... someone else copy this secure database into another computer which has ... default workgroup? ... have permission to open this database file. ... removed the default Admin user's permission to open databases in your secure ...
    (microsoft.public.access.formscoding)