#Shortcut menu bar access 2013 update#
#Shortcut menu bar access 2013 code#

You only need to run the VBA code once in the database to create the commandbar for the form. How to create a custom shortcut menu command that identifies the calling form/report? You should also take a look at this thread: In development, I would advise the reference be set as the intellisense does make the coding faster and less likely to have syntax errors (and you can compile the code to check for syntax more easily) once ready, you can make the afore mentioned changes. This may not be considered to be true late-binding however, the reference isn't set and that will help with portability between clients. > This is part one of MS's site Customizing the 2007 Office Fluent Ribbon for Developers (Part 1 of 3) AFIK, 2007 ribbon references are still valid in 2010+ however, that may not hold true in the futureĪt this point your original question has been answered so if we need to go in to more detail on the following please start a new thread.ġ) Remove any reference to the shortcut menu in your formsĢa) Application.Commandbars('AgrShortCut').DeleteĬreate a Shortcut Menu for a Form, Form Control, or ReportĮither you must use late binding or the reference to the Microsoft Office 15.0 Object Library (or the current version thereof) must be set to use the examples provided in this link.įor the 'late binding' set two constants msoBarPopup = 5 and msoControlButton = 1 both as long, typecast a variable as a undefined object, then set this object to the desired commandbar using I've used simply the mandbars._ where the underscore is the correct call to add the menu or the control as needed (that should make sense when you read the examples). I tend to early bind the ribbon during development and then switch over to late binding once everything is working.

> Take note, an update to the above link, Since Acc2010 it is possible to LATE BIND the ribbon call back thus, one no longer has to ensure that the interface library (Microsoft Office 1(2|4).0 Object Library) is properly referenced if late binding is implemented. (the tool I did use for Excel is the Custom UI Editor for Microsoft Office - it might still be available however, any decent XML editor will allow you do the same too and you should be able to add the ribbon schema for the editor to use for validation: Office 2010 Reference: Office Fluent User Interface XML Schema - the Excel files take a little extra work to get the ribbon into, Access is much simpler IMHO). I include the link to this site because it has one of the best set of reference materials for the Ribbon interface I've ran across since OFFICE2007 introduced the concept - as a matter of fact, if not in part for this site's reference materials, I would never have been able to develop my first Ribbon for Excel when Office2010 first rolled out and broke our custom workbook add-in menus! Mind you, I created that ribbon without their tool. so.Ī caution here, this site has its own ribbon creation tool that it sales, AFIK, is neutral about this tool as am I. The concept for writing the XML for the ribbon is very much the same for Word as in Access however, in Access the ribbon is quite often built within the Database using a usysribbons table. Unfortunately there's not a lot of information about creating and using Ribbons. instead you'll eventually have to use the ribbon and context based groups. IMHO, as the versions of office advance, the older style shortcut menus are going to be harder to use. You can also use RibbonX and XML to create a custom ribbon for your desktop database. Adding them to a custom Ribbon group is also supported. But you can make them appear on the Add-ins tab, or add them to a custom Ribbon group or the Quick Access Toolbar.Īccess 2003 Toolbars and menus are shown in the Add-ins tab on the Ribbon. You can no longer bypass the Ribbon interface and show Access 2003 toolbars and menus in Access 2013 as you could in 2007 and Access 2010. If you are trying to import one of the older style custom menus (mdb files are the older format) in to ACC2013/2016 you may be out of luck as a stand alone tab and/or pop-up as in ACC2003 however, it should be in the 'Add-Ins' ribbon tab as you've already discovered, and it does appear that you should be able to add a custom ribbon tab:ĭiscontinued features and modified functionality in Access 2013 (read more.)

#Shortcut menu bar access 2013 code#

#Shortcut menu bar access 2013 update#