Peter,
Ah. Sorry for the misunderstanding. Unfortunately, that's not possible. You could trick you users by writing code that does this--by using another database. But I don't think you'd gain anything. The whole bit of sharing computers is really a pain, because users so rarely take the care they should to switch properly. If there's any way the organization can spare $600, they can get another computer and be done with the whole mess for less than the amount they'll pay you to deal with it.
On the other hand, if all the users sharing the computer are of the same security level (all of the groups they belong to are the same), and your only concern here is tracking who's doing what, and you trust your users to be good about switching userIDs, you might be able to go about it a little differently...
Build a bogus user who is a member of exactly the same groups as the users in question, with a name like Multiuser and a password that all the users will share. (You might want to change that password every month and e-mail it to each of these people when you do.) Build code that pops up a special form when this user logs in. On that code, have a combo box that lists the user names of all of the people who will share this computer (cast your net broadly). Then make a way to "end the session" when a person is done with the computer, or when a new person shows up. This will just bring you back to that same form. Then, in all the places where you grab the username, use a function that grabs the username and, if it's Multiuser, substitues the value of the combo box of that form (which will never close, it will just go invisible).
Do be aware that this will lead to a relatively poor security situation, if that's a concern to you. But if there are people sharing computers, my guess that this is not a big concern to you.
How's that sound?
Jeremy
==
Jeremy Wallace
AlphaBet City Dataworks
Access Databases for Non-Profit Organizations
Please post in the appropriate forum with a descriptive subject; code and SQL, if referenced; and expected results. See thread181-473997 for more pointers.