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.
Best,