Hi.
If user-level security has been implemented on the database, then the user
must close the database application first, so that another user can open the
database with a different set of permissions. It's not possible to change
the CurrentUser during the session, so whoever opened the database
application will have his permissions applied to all who use the database
application while it is open. Logging out so that another user can log in
under different credentials requires closing the database, then opening it
with the next user authenticating with his own User ID and password.
If a home-grown security method has been implemented instead of user-level
security, then it may be possible to log out and log in under the default
Admin user's credentials without closing the database application, but it
depends upon the method used to log in and log out. Of course, everyone who
logs in and logs out would have the same user-level permissions granted to
the Admin user who, as as member of the Admins group, has unlimited
permissions. And home-grown security is easily bypassed, so it probably
isn't worth the trouble.
HTH.
Gunny
See
http://www.QBuilt.com for all your database needs.
See
http://www.Access.QBuilt.com for Microsoft Access tips.
(Please remove ZERO_SPAM from my reply E-mail address, so that a message
will be forwarded to me.)
- - -
When you see correct answers to your question posted in Microsoft's Online
Community, please sign in to the Community and mark these posts, so that all
may benefit by filtering on "Answered questions" and quickly finding the
right answers to similar questions. Remember that the best answers are often
given to those who have a history of rewarding the contributors who have
taken the time to answer questions correctly.
