User Authentication

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

Guest

I am trying to write codes for two levels. One is user level for data entry
and make changes only on the same day the user does the data entry. Another
one is supervisor level that the supervisor can make changes and delete the
records.

I will appreciate anyone who will give me a hand on how to write codes for
this kind of user authentication.

Best regards,

sc
 
Creating your own type of "home-grown" security system can easily
be bypassed with people with sufficient Access knowledge. It would
probably be better to implement User Level Security (a built-in feature
of Access) on this database so it will be more secure. If you have
never used ULS before I would strongly suggest you review all of
the following information available here:

http://www.ltcomputerdesigns.com/JCReferences.html#Security

It is a difficult concept to grasp the first few times so it is recommended
that you practice on dummy databases until you are really comfortable
with the process.

There are times, however, when ULS is overkill and creating your own
security *system* is OK. The choice is yours to make, you just need
to carefully weigh the pros and cons.

Good luck with your project.
 
sc:

In my applications I always have the following regarding roles:

1. A user table that contains the user's network login name, their full
name and their role.

2. Code in my startup form that compares their actual network login to
the user table to see if they are an authorized user of the app. If not
I give them an appropriate message and exit them from the app.

3. Code in startup form that stores the user's role in the user table
in a form in the app that stays open and provides a source of
information throughout the session regarding the user's rights and other
system information. See frmSecurity below.

4. Code in startup form that prevents them from seeing certain parts of
the app based on their role. For example certain tabs in a tabbed form
can be made not visible in design mode, and only made visible for
certain roles at startup:

if forms!frmSecurity.form!txtRole = "supervisor" then

Me!pagEditTab.Visible = True

end if

4. Code in an edit form that can take away edit and delete rights for
the form based on their role, for example:

if forms!frmSecurity.form!txtRole <> "supervisor" then
me.Allowedits = false
me.Allowdeletions = false
end if

Bill
 
Back
Top