Set password for modification

[Guest]

I am feedup with someone going into the database and modifying it all the
time. I would like to setup a password so that noone is able to modify the
tables, queries, reports, forms, etc... How Do I do that?

 

[TC]

If you create an MDE copy of the database they will not be able to
modify the design or coding of the forms, reports and modules. Would
that be enough? Check the online help for MDE. Do not discard the MDB -
just create, in addition, and MDE, and give your users the MDE. Keep
the MDB for yourself.

HTH,
TC

 

[tina]

if the database sits on a server and is accessed by multiple users, it
should be split into a "backend" db (tables only), and a "frontend" db (all
other objects, and links to the BE tables). each user should have a copy of
the FE db on his/her hard drive, and you (as the developer) should keep a
"master" copy of the FE db that you will modify as needed, and then
redistribute copies of the modified db to the users. you can add a password
to the BE db *before* setting the table links in the FE master db. that way
the linked tables will work, but the users can't open the BE db to modify
the tables' design. if you want to stop users from modifying the forms,
reports, etc in their own copy of the FE db, you can make a .mde file from
the master FE db and distribute the .mde file to your users. a .mde file
only protects forms, reports, and modules, so the queries (and the macros, i
believe) are still vulnerable.

probably the best way to fully protect both the FE and BE databases is by
implementing Access User Security. but that's not a trivial task; you'll
need to read up on it thoroughly and practice implementation on a copy of
your database before doing it "for real".

hth

 

[Guest]

I have done what you said but I receive and error message (Invalid Password)
when I tryo to use the "Linked Table Manager." I need the users of the
frontend to have access to the backend to update the existing tables but I
don't want them to be able to link to them from their own database.

I am searching for code to see if there is a way to pass the password to the
backend so users are able to update but it will be a secure backend.

 

[Joan Wild]

It sounds to me like you've set a database password on the backend. If so,
you'll need to go to the tables window in the frontend and delete all the
links. Then File, Get External Data, Link Tables and locate the backend.
You'll be prompted for the password, which will now be stored with the
links.

You should be aware that it is trivially easy to hack the database password.

 

[Guest]

You are correct. What would you recommend as the best method to secure a
backend database? I realize that anyone can easily hack my password but that
is the case no matter how I do it. There will be approx 100 people using it
so user level security seems to be too much administration.

I appreciate your quick response and I will definitely pursue any ideas that
you offer. What about the encryption tool within Access? Is it worth looking
into?

 

[Joan Wild]

Users need access to the file in order to use Access. There is nothing you
can do that is absolutely secure. You can just put up barriers, and if your
users aren't inclined to try to get by them, then you won't have a problem.

The database password may be sufficient in that case.

But if you need absolute security, you should use a server-based backend
like SQL Server or Oracle.