Re: Database properties

On Jul 29, 1:10 pm, "paii, Ron" <n...@xxxxxx> wrote:
I execute that type of code on the copy used to update the end-user's
front-end. That way they have the settings on the 1st login.

"Jim Devenish" <internet.shopp...@xxxxxxxxxx> wrote in message

news:919cbf46-0b19-4de4-a8d4-ae84fd45dc71@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx

I wish to control which users can and cannot alter the toolbars.  The
opening popup window invites them to login.  Immediately after this, I
have the code:

CurrentDb.Properties("AllowToolbarChanges") = isManager
CurrentDb.Properties.Refresh

isManager is a function that returns true/false

This works (up to a point) but I am caught by the final line in the
Help that says:
"This property's setting doesn't take effect until the next time the
database opens"

So, it would seem that I have to quit the database and get the user to
log in again. (But then, of course, not repeat this procedure!)

Is there any way in which this change can be made for the current user
without them having to log in again?

Or is it possible to quit and then (from code) automatically log that
user in again?

But this assumes that a particular front-end (on a specific machine)
is only used by one user. This is not the case here. Different users
may, from time to time, log in to a specific front-end. I want to
have the behaviour different for each user - not for each front-end.

Jim

.