login system

[mrcunknown]

Hi everyone, I am looking for a login system (with preference 5 roles and an administration where I can see who is logged in and who can add users). I have already searched the internet, but can not find the right one. my knowledge to make it myself is too small. I hope that someone can help me :-)

[June7]

This is a common topic in forum. Many threads with discussion and examples. You just have to do research, make an attempt, and when you encounter specific issue, post question. Here is one for a start that shows my approach https://www.accessforums.net/showthread.php?t=23585

[isladogs]

Here's another from my website http://www.mendipdatasystems.co.uk/p...gin/4594469149
As June says, there are lots of examples around.

[mrcunknown]

thank you. As you know, I am very impressed with your login system. only I do not know how to make the form after logging in. but I think your login is super!

Greets marc

[June7]

Did you mean "make the form open after logging in"? Why are you stumped by that? If user passes login validation, open form:

DoCmd.OpenForm "form name"

[mrcunknown]

In case of the system for isladogs. Im not sure how the forms should look like aver loggin in.... so every role has his own level. Sorry for my bad English

[June7]

Depends on what you want to happen. Do you want to filter records or enable/disable buttons?

[mrcunknown]

The idea is to enable/disable buttons. After loggin in the user see the buttons he or she have access to like a switchboard

[June7]

Options for passing info to the form to open: 1) OpenArgs argument; 2) filter criteria; 3) TempVars or global variable; 4) set textbox value

Code posted in my link passes value with OpenArgs. I have since modified to apply filter criteria. The Menu form is bound to Users table.

DoCmd.OpenForm "Menu", acNormal, , "UserInitials='" & Me.tbxUser & "'", , acWindowNormal

Then code behind Menu form manages itself to enable/disable buttons and perform other actions:

Private Sub Form_Open(Cancel As Integer)
Me.cbxUser = Me!UserInitials
If Me!Permissions = "admin" Then
    If Not IsNull(DLookup("DateEnter", "UserComments", "Isnull(DateReview)")) Then DoCmd.OpenTable "UserComments"
    If Format(Now(), "hhmmss") <= "080000" And Weekday(Date) = 2 And ((Month(Date) >= 6 And Month(Date) <= 9) Or Month(Date) <> Month(DLookup("ConstructionExtract", "Updates"))) Then
        ConstructionExtract
    End If
End If
If Me!Permissions = "staff" Then
    Me.cbxUser.Visible = False
    Me.btnAdmin.Visible = False
    Me.btnCost.Visible = False
End If
If Me!Permissions <> "admin" Then Call SetAccessXCloseButton(False)
Me.btnSample.SetFocus
End Sub

[isladogs]

thank you. As you know, I am very impressed with your login system. only I do not know how to make the form after logging in. but I think your login is super!

Greets marc

Oops - sorry Marc - didn't notice your user name when I answered the post!
If it helps, I'm going to work on my 'Pro version' this week

[beilstwh]

Personally I never have internal login systems. I simply grab the windows network login from windows and the privileges are assigned from that user name. Since everyone should have their own network login, let windows handle the authentication.

[isladogs]

Personally I never have internal login systems. I simply grab the windows network login from windows and the privileges are assigned from that user name. Since everyone should have their own network login, let windows handle the authentication.

That's fine in cases where the privileges are consistent in both the network and in each of your apps. However, in all the network apps I have designed, that isn't the case.
In addition, in many environments, users may need to login to an app on a system where another user is logged in to the network.
The system you describe cannot handle that scenario

[June7]

What beilstwh describes is what I do and is reflected in my posted code. Security is not really reason for login. I just need to know who is interacting with the db because some records need to document who is doing the edits. The only time user sees 'login' form is the first time they ever use the db so I can create new record in Users table. I do disable a couple of buttons based on privileges and conditionally run some processes but beyond that, if they have Windows login then they are authorized to use db. The network firewall is far better than anything I could do.

[Micron]

The only time user sees 'login' form is the first time they ever use the db so I can create new record in Users table

Sounds like you've never made a db that was visible to "outsiders" that shouldn't be allowed in.

[June7]

Correct, strictly in-house use.