If you don't have a user table, you should. As you progress, you will find more and more reasons for accessing it. Here's most of the field names for one I use:
LoginID |
Perm |
Fname |
Lname |
Level |
Active |
LoggedIn |
SndReqEmail |
SndRgaEmail |
ContCntr |
Email |
The loginId is the computer loginId (Google fosUserName). I get that value and query tblUser. If they're not there or they're inactive, they don't get in - no password needed, or will be forgotten, or needs to be renewed. Level allows some functionality and not other. LoggedIn lets me know who's in. Fields 8 and 9 determine if they get certain emails when required. Last field is the email address. If you think this table could prove useful down the road, better to start now.
RuralGuy's suggestion to hold any of these values would work and is probably the easiest. If you progress enough, you can create a custom user object and assign all the user properties to it on startup. This is what I do and if I want to put their name in a textbox, I'd write Me.ctlMyControl = dbUser.Fname