Relative novice using Office 365 on a windows 10 64bit PC. I’ve converted a db from 2007 to 2016 in which I’m working on setting up security features: specifically removing the options from the file tab on startup via a custom ribbon. The approach I’m mimicking uses a table to draft an XML code (below), then changing the Ribbon name in options\Current Database to the created ribbon.
<customUI xmlns="http://schemas.microsoft.com/office/2009/07/customui"><ribbon startFromScratch="false"></ribbon><backstage><button idMso="ApplicationOptionsDialog" visible="false"/></backstage></customUI>
The functionality works, however when I hold the shift key down to open in developer mode to bypass the custom ribbon, it still opens with the custom ribbon. The only work around I’ve found is to setup the custom ribbon in a table stored on the back end and change the code there when I want access to the front end.
Is there an oddity in access 365 that doesn’t allow the shift key to open access in developer mode? The coding I’m following was developed for 2013. I have verified Sticky Keys are turned off and after looking through the codes I've added, I don't see anything that references "allowbypasskey"
Any suggestions would be greatly appreciated.