{"id":2063,"date":"2019-04-04T15:15:59","date_gmt":"2019-04-04T15:15:59","guid":{"rendered":"http:\/\/elbsolutions.com\/projects\/?p=2063"},"modified":"2022-02-03T11:24:27","modified_gmt":"2022-02-03T17:24:27","slug":"pre-setting-trust-access-to-the-vba-project-object-model-for-users-via-registry","status":"publish","type":"post","link":"https:\/\/elbsolutions.com\/projects\/pre-setting-trust-access-to-the-vba-project-object-model-for-users-via-registry\/","title":{"rendered":"Pre-Setting ‘Trust access to the VBA project object model’ for users via registry"},"content":{"rendered":"\n

There are some pretty cool “on the fly” programmatic things we can do with the VBA references like deleting “MISSING” references (which break code that is referenced UNDER these missing references- that is why they need to be fixed). But to do so requires that the user checks the box ‘Trust access to the VBA project object model’ which is buried deep (in typical Microsoft fashion). The Ribbon to check this manually is in the popup window accessed by File->Options->Trust Center->Macro Settings. Instead of writing code to tell the user what to do – why not get a registry change on all the target computers first. This article gives the *hint* on how to do that<\/a>. I have 32bit Office (on purpose – so I don’t forget about those users) but everyone should have 64bit. So – there are a few registry keys that should get set. <\/p>\n\n\n\n\n\n\n\n

[HKEY_CURRENT_USER\\Software\\Microsoft\\Office\\15.0\\Excel\\Security]
\n“AccessVBOM”=dword:00000001<\/p>\n\n\n\n

[HKEY_CURRENT_USER\\Software\\Microsoft\\Office\\15.0\\Excel\\Security\\Trusted Locations]
\n“AllowNetworkLocations”=dword:00000001
\n“AllLocationsDisabled”=dword:00000000<\/p>\n\n\n\n