Password (this is a two-parter)

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I created a Database in access. The database has three tables that belong to
three different people. I want them all in this database because I can run a
query with no problem. Here is my dilemma and it’s a two-parter. I want to
put a password on each table. Everything I look at lets me put a password on
the database, but not on the table. Next, I would like for it to tell me that
I cannot get into table 3 (even if I have the password) because someone is
updating it. If it lets us both in, that destroys the point of Access.

Please help.
 
First, you would want to assign userid and password to each USER. Then you
can limit their access to objects in the database. You could allow "john"
to have access only to table1 for example.


Second, you would not want your users accessing the TABLE directly, they
should go through forms or queries.

Third, allowing multiple people to access data at the same time IS THE WHOLE
point of a shared database. Access will take care of not letting them
'step' on each other's data. Not sure why you would want to prevent me from
viewing a record simply because someone else was in the database adding a
new record, or running a report.

For more information on securing your database, read and reread the
following. Make sure to work off a copy.

Security FAQ

http://support.microsoft.com/?id=207793



The Security Whitepaper is also worth reading to help you understand.

http://support.microsoft.com/?id=148555



Joan Wild:

www.jmwild.com/AccessSecurity.htm



Lynn Trapp

http://www.ltcomputerdesigns.com/Security.htm











Rick B
 
Another option would be to create separate front-end databases for each
user. In these databases, you would link to the back-end database where all
your tables live.

The front-end used by User1 would only link to Table1. The front-end used
by User2 would only link to Table2, etc.

YOU could still access the backend and run queries on all three tables or
(better yet) you could create a fourth front-end database that had all three
linked tables.

Rick B
 
Back
Top