current user name display on form

[Micron]

it might be the dlookup function to carry out this particular command does not work in Access 2016

If you mean me, then that's not what I meant to imply. I meant that sometimes improper syntax will run or compile in earlier versions but will fail in later ones. In those cases, it's the syntax of the function call that is the problem, not the function itself. As for me, I still have no idea where or what CurrentUser is in your code.

[cariboy]

i have attached a shell copy of the database. use this login information username: jbrowne password: password

[June7]

Every module should have Option Explicit in header. This can be set to occur automatically when module is created. On the VBA editor menu: Tools > Options > Editor > Require variable declaration

The username is not filled in when user is required to change password. Subsequent logins work.

Form tblUser AllowAdditions property should be set to No. Password EnterKeyBehavior should be set to Default. Why would you allow new line in a password string? Also, only Password textbox should be editable. The other textboxes should be disabled.

On Login form change TabOrder of controls so textbox gets focus when form opens. I would not use Popup or Modal. SetFocus for textboxes is not working and haven't figured out why.

Suggest naming Command1 something more descriptive.

Consider:

Option Compare Database
Option Explicit

Private Sub Command1_Click()
Dim ID As Integer
Dim UserName As String
Dim AccessLevel As Integer

If IsNull(Me.TxtLoginID) Then
    MsgBox "Please enter LoginID", vbInformation, "LoginID Required"
    Me.TxtLoginID.SetFocus
ElseIf IsNull(Me.TxtPassword) Then
    MsgBox "Please enter Password", vbInformation, "Password Required"
    Me.TxtPassword.SetFocus
ElseIf IsNull(DLookup("UserLogin", "tblUser", "UserLogin ='" & Me.TxtLoginID & "'  And password = '" & Me.TxtPassword & "'")) Then
    MsgBox "Incorrect LoginID or Password"
Else
    ID = DLookup("UserID", "tblUser", "UserLogin = '" & Me.TxtLoginID.Value & "'")
    UserName = DLookup("[UserName]", "tblUser", "[UserLogin] = '" & Me.TxtLoginID & "'")
    AccessLevel = DLookup("UserSecurity", "tblUser", "UserLogin = '" & Me.TxtLoginID & "'")
    If Me.TxtPassword = "password" Then
        MsgBox "Please Change Password", vbInformation, "New Password Required"
        DoCmd.OpenForm "tblUser", , , "[UserID] =" & ID, , acDialog
    End If
    DoCmd.OpenForm "MAIN SCREEN"
    Call Security(AccessLevel)
    Forms![MAIN SCREEN]![TxtUser] = UserName
    Forms![MAIN SCREEN]![txtsecurity] = AccessLevel
    DoCmd.Close acForm, "Login", acSaveNo
End If
End Sub

Sub Security(UserSecurity As Integer)
Select Case UserSecurity
    Case 1  'Admin
    
    Case 2  'User
        'me.AllowEdits = true
        MsgBox "Your User Level Is 'User'"
        Forms![MAIN SCREEN]!CmdAdmin.Enabled = False
End Select
End Sub

Option Compare Database
Option Explicit

Private Sub CmdSaveNPW_Click()
DoCmd.Close
End Sub

Private Sub Password_BeforeUpdate(Cancel As Integer)
If Me.Password = "password" Or Me.Password.OldValue = Me.Password Then
    MsgBox "Invalid password."
    Cancel = True
    Me.Password = Null
End If
End Sub

[cariboy]

thanks for your suggestions and i will look into them, were you able to solve my initial issue....Making that button that says admin on the main screen available or not based on the user login and making the user's name appear on "Main Screen"? is the code posted after your last reply the updated code to make this work, just a quick look at it and it looks a little different from the one i post, i could be wrong

[June7]

Yes, the code is a bit different. Wait, I was so focused on the Username issue, forgot to look at the Admin button.

I just noticed the code in the MAIN SCREEN Load event which is attempting to do what is also done in the Login form - why? Which procedure do you want? You never posted the Load code nor even mentioned it. The textbox does not have value when the Load event runs so this negates whatever was done by the login form code.

If you want code in MAIN SCREEN to manage itself (which is my preference), then suggest passing values via OpenArgs argument of OpenForm and use Open event to set controls.

[cariboy]

June7 thanks for adjusting the code...I'm still to update my database with what you suggest...once i do i will let you know how that worked. Sorry I really thought i did mention that restriction of the "Admin button". To be honest i'm at a total lost as to the other things you said in your last post. The main screen should do this; after login in, the "Main Screen" load, with the user name at the top right hand (is your new code doing this?) and the "Admin Button" enable or disable based on the user's security...is this already being done at the login screen level? what do you mean by "If you want code in MAIN SCREEN to manage itself (which is my preference), then suggest passing values via OpenArgs argument of OpenForm and use Open event to set controls." I'm not too verse in coding

[June7]

Exactly what do you not understand - OpenArgs? Two procedures are setting controls of the MAIN SCREEN form and conflicting. Eliminate one.