Setting up a signon screen for additional security

  • Thread starter Thread starter PAUL
  • Start date Start date
P

PAUL

In addition to the delivered security of Access 97, I
want to limit tables to certain users based on different
areas of the company, so users can't see all the data,
only that related to them.

I want to have a signon that would involve a password
that could be validated against a table that would be
maintained by the Administrator.

Any suggestions on how to accomplish this would be great.

Thanks,
Paul
 
Why in the world would you want to code up a whole bunch of things when you
gone so far as to use the built in security?

Simply make a new security group, and then join those tables to that
security group. It is then a trivial matter for your administer to add those
users to that group to given them security.

If you are actually assigning individual security to users (be it forms,
tables, reports or whatever), then you ARE DOING IT ALL WRONG!

You NEVER want to assigning security of a form, or report to a individual
user. By doing so, you start placing security into the actual application.
Further, it becomes completely un-manageable if you have a few users, as
then you have to make a LOT of settings for each user. The correct way is to
ALWAYS assign forms, tables, reports etc to a security group, and then you
assign users to THAT security group. This means that NO user security is
EVER placed in the database, but it all stays in the work group file.
Further, doing this will give your administer complete control over who can
use the table(s), and it will cost you virtually NO code. Also, this
approach is manageable, and you can update the front ends without loosing
security settings that THEY change. Thus, you can even work on new software
updates, and use a copy of their workgroup file. They are free to change
security settings, and when you send them a new update to their software, NO
security settings will be lost.

So, why write a bunch of code, when security offers you the features you
need?

If your security is setup correct, then you simply fire up the workgroup
manager, and assign to each user this security group. The whole idea behind
the built in security is to eliminate the need to code this.

Of course, I never did like the workgroup security manager. If you spend a
few hours, you can build a nice screen, and not even bother your users with
the security manager. So, write you own! Here is some examples of what I
mean. Note how much easer a simply little ms-access form is then the
workgroup manager. All of the following screen shots are based on ms-access
security.


http://www.attcanada.net/~kallal.msn/Articles/UseAbility/UserFriendly.htm
 
Back
Top