Forum Discussion
Runtime Access Options
- Aug 28, 2021
In my experience most users find the warnings irritating
Personally, I wouldn't give users the option but its your database and can be done if you think its really worth the effort,.
As users have no means if accessing Access options in runtime, you could consider this as a workround
1. Have a table tblUsers to include these fields:
UserName - text (based on Windows network login or an application login form
ShowWarnings - yes/no (boolean) - set default value as false
2. Have a settings form linked to that table where users tick a checkbox if they want to see warnings throughout your application
3. Create a public function GetUserWarningsState to recall that value. Something like this would work (or you can use tempvars)
Public Function GetUserWarningState() As Boolean GetUserWarningState = DLookup("ShowWarnings", "tblUsers", "UserName = '" & Environ("USerName") & "'") End Function4. Finally each time you run an action SQL statement, modify the code as follows:
'show warnings only if user has specified their use If GetUserWarningsState = False Then DoCmd.SetWarnings False DoCmd.RunSQL "Your SQL string here" DoCmd.SetWarnings True 'always set/reset warnings true afterwards
Thank you for your reply.
You have understood the problem and solve the problem on the programmer's side. Unfortunately in this way all users who will use my application will no longer have notifications.
My wish would be that every user could choose whether to have them or not. I achieve this when the user has the full Access product by acting on the Options.
How can I access the Options with the runtime?
Thank you again.
In my experience most users find the warnings irritating
Personally, I wouldn't give users the option but its your database and can be done if you think its really worth the effort,.
As users have no means if accessing Access options in runtime, you could consider this as a workround
1. Have a table tblUsers to include these fields:
UserName - text (based on Windows network login or an application login form
ShowWarnings - yes/no (boolean) - set default value as false
2. Have a settings form linked to that table where users tick a checkbox if they want to see warnings throughout your application
3. Create a public function GetUserWarningsState to recall that value. Something like this would work (or you can use tempvars)
Public Function GetUserWarningState() As Boolean
GetUserWarningState = DLookup("ShowWarnings", "tblUsers", "UserName = '" & Environ("USerName") & "'")
End Function4. Finally each time you run an action SQL statement, modify the code as follows:
'show warnings only if user has specified their use
If GetUserWarningsState = False Then DoCmd.SetWarnings False
DoCmd.RunSQL "Your SQL string here"
DoCmd.SetWarnings True 'always set/reset warnings true afterwards