If "CurrentUser" = the user who is logged onto the Windows machine, then no. If you are concocting that ID yourself, then yes, just make a form to do it.
Want to get great answers to your Tek-Tips questions? Have a look at FAQ219-2884 or FAQ222-2244. Basics at
"CurrentUser" captures the user who has logged into Access. This is a "Common Expression" within the program itself. We are trying to avoid having the user exit and re-log into the program everytime they need to perform other tasks unassigned to that specific user id. I was hoping there was a way to simply give a command to change the CurrentUser something like CurrentUser=XX.
There is one global user id shared by a specific dept which accesses a totally different database via ODBC, otherwise all users have their own ids. The menu and tasks are user specific. The main user of the global id has 2 machines, however we are removing one of them tomorrow, so she needs access to both menus from the same workstation. The "CurrentUser" variable needs to switch when I pop up the user specific menu, so when she goes about the tasks from that menu it correctly identifies her and not the global user id. There are several controls in place that respond to the user id's, so that data does not inadvertently end up within the wrong database, so it is imperative that correct user id's be used for the various tasks.
If there is no way to update the variable/expression
"CurrentUser", then I will probably opt for giving her another copy of the application and getting her to run 2 sessions when required.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.