asked on

Configure FrontEnd.mdb so that Joe can Use Access Special Keys (and VBA)

Our FE.mdb front end database runs in "user mode" which means: special keys off; navigation off; full menus off; etc
But Joe needs a "tester mode" with special keys ON.

Currently, we accomplish this manually: v
Joe opens FE.mdb then clicks File > Privacy Options > Current Database > Use Access Special Keys > OK
After closing and reopening FE he is in "tester mode".

But he needs to do this every day because our network signon script always recreates c:\front end\fe.mdb from the server's FrontEndMaster folder.

I am planning on modifying the signon script so that Joe's refresh comes from a FrontEndSpecial folder which I must carefully maintain. Is there a cleaner approach?

ASKER CERTIFIED SOLUTION

Scott McDaniel (EE MVE )

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

Robert Berke

ASKER

That comes close, but is not ideal.

The following Autoexec code toggles the setting, but the change does not take effect until Access is closed and reopened.

    If environ("username") = "Joe" Then
        If CurrentDb.Properties("allowspecialkeys") <> True Then
            CurrentDb.Properties("allowspecialkeys") = True ' this immediately saves the change to c:.. FE.mdb on disk
            MsgBox "Joe: At your convenience, please close and reopen the address book. (This will help Bob debug future problems)"
        End If
    End If

Open in new window

This means Joe must redo the change when he signs into the network every day.
In contrast, changing the login script means that Joe never has to do anything special. But the downside is that everytime I change the front end, I must make 2 versions, one with special keys off for most users and one for Joe that has special keys on. I change the front end several times a year, so the big downside is that I might forget to make a special copy.

I hope someone can come up with something better

Scott McDaniel (EE MVE )

That's the way all those types of things work - you set them, then the next time Access opens it uses the new settings.

You could create a "launcher" that would (a) set the value appropriately and then (b) close the Access database and finally (c) open it again.

You could also use the SOON utility here: http://trigeminal.fmsinc.com/lang/1033/utility.asp?ItemID=8

SOON = Shut One Open New. I've used it before to basically what you're doing.

Robert Berke

ASKER

SOON would probably do it. but I like your first solution better and will give it the points.

I might even consider letting all users have special keys turned on.

Normally I would say that was crazy, but It turns out that 8 of our client computers are using Access Run Time environment, which always ignores special keys.

only Joe and 2 others have the full access. and all 3 are totally trustworthy.

Still it is probably a bad idea because there is talk about office 365 for everybody. If that happens all 11 users would have full Access which is way too risky.

Anyway thanks for the help.