Closed damorinCan closed 1 week ago
As someone who operates in a "high security" environment, I can almost guarantee this issue is caused by your cyber policy blocking macro execution.
If you can have them add an exception for Access Macros, that'd be the best way.
What our IT group did was add a specific folder an access file has to operate in for the exception to be valid. This allows the IT / OT group to reduce the attack surface (it is highly unlikely other access / office products will know to move to the "special" folder), and for us to run Access VBA macros (which at the time we did this couldn't be signed, that's changed, but the currently delivered file doesn't have signed macros).
What I recommend:
c:\users\[Username]\Documents\[OurGroupName]-Tool-Dev\
C:\Users\[Username]\AppData\Local\[DatabaseRelease]\
for everyone to operate the delivered product.If that doesn't work, you may need to uncheck "Use Ribbon Addin"; but the ribbon is such a nice thing try first to use it.
Your IT group may also be interested in this: https://github.com/joyfullservice/msaccess-vcs-addin/wiki/Security-Considerations
Did you resolve this? If so, can you close the issue? If there's more to be determined on the add-in side, we can troubleshoot.
Yes, we found another way around it; it's to run the 'cmd' file to complete the installation.
Thanks.
@damorinCan, can you close this if it's fixed?
Done.
Thanks!
Hi,
In Windows 10, when clicking on the 'Version Control.accda' and clicking on "Install Add-In', this is causing the following error:
ERROR: Unhandled error, likely before `On Error' directive Source: .Unknown.LogUnhandledErrors.
In Windows Security, the description is:
App or process blocked: MSACCESS.EXE Blocked by:Attack surface reduction Rule: Prevent all office applications to create child process
As a note the "Rule" was in French on my PC, I translated this to my best knowledge.
Before asking my IT department to add an exception, can someone confirm this is not a problem ?
Thanks,