Store logged in username in a variable

[Hammilton]

Hello, I have a database that I'm still working on. I've made some progress but I'm hung up on more than I've completed unfortunately. I could use your help with solving this and then I can fix a number of problems I'm having.

In my database, the user logs in, and the log in works flawlessly. However, once that user logs in I'd like to store his username and fullname in a variable. I can't figure out how to use variable strings from one form to the next. For one, I'd like to display the username of the logged in user once they're logged in.

I also need that information to compare against in the password changing screen. I don't want the user to need to enter their username in order to change their password, too, just the old password.

You've been extremely helpful and I am very grateful for your assistance.

Thanks guys! (and gals)

[June7]

Common topic.

I save the user info on a form that never closes (MainMenu) so that it is always available for reference.

Alternatives:

1. declare a public variable in a general VBA code module - the variable can be referenced from any VBA procedure in the db - drawbacks are cannot be referenced in Access objects and if code execution is interrupted, the variable loses value (this can be annoying during development and debugging)

2. TempVars - advantages are can be referenced in Access objects and do not lose value if code execution is interrupted but may be a little harder to understand how to use than VBA variables

[Hammilton]

I like the saving it on the main form, but how do I get it from the login form to the main form? It's a variable on the login screen, you log in, that form closes and the new form opens.

I see the question asked but maybe I'm dumb, and I probably I am, but I can't figure it out.

Thanks!

[June7]

1. open MainMenu

2. set value of textbox on MainMenu

3. close login form

Or pass info using OpenArgs https://www.accessforums.net/access/...gin-23585.html

[Hammilton]

Okay, this is the code I have:

Dim rs As Recordset
Dim db As Database
Dim tempUserID As String

Set db = CurrentDb
Set rs = db.OpenRecordset("Users", dbOpenSnapshot, dbReadOnly)

rs.FindFirst "Username = '" & Me.txtUserName & "'"

If rs.NoMatch = True Then
Me.lblIncorrectUsername.Visible = True
Me.txtUserName.SetFocus
Exit Sub
End If
Me.lblIncorrectUsername.Visible = False

If rs!Password <> Nz(Me.txtPassword, "") Then
Me.lblIncorrectPassword.Visible = True
Me.txtPassword.SetFocus
Exit Sub
End If
Me.lblIncorrectPassword.Visible = False
If rs!Admin = True Then
DoCmd.OpenForm "frmMain"
frmMain.lblUser = Me.txtUserName
DoCmd.Close acForm, Me.Name

Else
DoCmd.OpenForm "frmUserMain"
DoCmd.Close acForm, Me.Name
End If



The code highlighted in red is what's not working. What am I doing wrong?

[June7]

Try:

Forms!frmMain.lblUser.Caption = Me.txtUserName

[ssanfu]

Because of the "lbl" prefix, "lblUser" would indicate to me the object is a label. You have to use the "Caption" property for labels. Labels do not have a "Value" property.

Forms!frmMain.lblUser.Caption = Me.txtUserName




June beat me ....again

[Hammilton]

10-4, works like a charm.

When do you use the ! symbol? Anytime I'm referencing something that's open on another form or report?

Can I use rs!Full Name instead of the value that's in the textbox? That's what I'd really like to do. However, there's a space in that, and I'm not sure how to use it when there's a space in it.

[ssanfu]

Best option - remove all spaces in object names.

Option #2 - try rs![Full Name] or rs("Full Name")

[June7]

I use the dot to invoke intellisense popup tips.

I use the bang (!) when referencing field names and in some other uses as in referencing object such as the Forms!formname syntax.

I would probably use a DLookup() instead of opening a recordset object.

[Micron]

post #2 is one of the best explanations of ! versus . that I've seen. What I've read on the subject at MS for VB4 seems to be echoed here, but in a way that the writer expounds on how the use of either character is translated by the application interpreter.
http://www.utteraccess.com/forum/Me-Me-t1644997.html&pid=1645019&mode=threaded#entry16450 19

For those who may be quick to point out, I realize VB4 (or any generation of it) is not VBA per se.

[Hammilton]

Thanks, your help here enabled me to solve the one problem I had initially, and thanks to what I learned I was able to do a lot of other things I was hung up on.