Access Options - Client setting (1 Viewer)

Gismo

Registered User.
Local time
Today, 16:43
Joined
Jun 12, 2017
Messages
548
Hi All,

i need to give access to my DB to quite a few users
when a user opens access for this first time, the clients settings under access options are all set to confirm record changes / document deletions / Action queries

how do I make these inactive when a user opens the DB for the first time?

also, how do I make the DB location a trusted location for a security warning on first opening the DB?
 

arnelgp

error reading drive A:
Local time
Today, 21:43
Joined
May 7, 2009
Messages
9,925
just instruct the user that on the first time opening the db, a security warning will appear and
that they need to acknowledge it.

on the first question you add an autoexec macro that calls a function
which in turn set/unset the confirmation dialog.
 

Gismo

Registered User.
Local time
Today, 16:43
Joined
Jun 12, 2017
Messages
548
just instruct the user that on the first time opening the db, a security warning will appear and
that they need to acknowledge it.

on the first question you add an autoexec macro that calls a function
which in turn set/unset the confirmation dialog.
Thank you

by any chance, could you please provide code for autoexec?
 

theDBguy

I’m here to help
Staff member
Local time
Today, 06:43
Joined
Oct 29, 2018
Messages
11,199
Thank you

by any chance, could you please provide code for autoexec?
Hi. See if you can find some of them here. I would also recommend you turn them back on when your db closes.
 

Isaac

Well-known member
Local time
Today, 06:43
Joined
Mar 14, 2017
Messages
1,513
how do I make these inactive when a user opens the DB for the first time?
The way I would recommend doing it is to wrap any code that performs those actions like so:
Code:
On Error goto Errhandler

...any code here

DoCmd.SetWarnings False
...Your code to perform the action query or object deletion
DoCmd.SetWarnings True

Exit Sub/Function
Errhandler:
...whatever message
DoCmd.SetWarnings True
...Rather than trying to set them to, essentially, Off/False, permanently.

This recommendation assumes that you develop applications for end users, and do not allow end users to perform any design-type of action.
 

isladogs

CID
Local time
Today, 14:43
Joined
Jan 14, 2017
Messages
13,616
By definition, client settings cannot be 'locked' by the developer.
All you can do is prevent end users accessing Access options but you can't overrule previously entered settings.

The only guaranteed way to set the location as trusted when the app is first opened is to distribute your app using a professional installer application.
Doing so allows the installer to create trusted location registry entries so these are in place before the app is used for the first time
Otherwise any security measures you impose can easily be circumvented by a knowledgeable end user using the shift bypass to open the app whilst it is still 'not trusted'
 

Users Who Are Viewing This Thread (Users: 0, Guests: 1)

Top Bottom