The ribbon doesn't appear after saving

WKL Forms Object Library 1.49 or later, Microsoft 365 Access; a ribbon saved with the ribbon designer, with WklRibbon.Save, or with the build tool (ribbonModel).

Access reads USysRibbons and the database property CustomRibbonID only when the database opens, so a saved ribbon can't appear any earlier. Other causes:

• The module basWklRibbon is missing: Save writes it after the calling VBA procedure ends, so if the database was closed in that same procedure, the module was never written.
• The WKL Forms Object Library isn't registered for the bitness of Office: the module can't create the runtime, and every element stays hidden (fail closed).
• The conditions hide the elements: the profile, the kind of database, or the function of a condition doesn't match.
• Access rejected the XML of a ribbon written by hand alongside the model; it reports this only when File › Options › Client Settings › Show add-in user interface errors is on.

1. Close the database and open it again.
2. In the VBA editor, check that the module basWklRibbon exists. If it doesn't, open the ribbon designer, save again (OK), and then reopen the database.
3. In the Immediate window, ? WklRibbonObject().Profile must return without an error; an error means the components aren't registered (see How to: Install the released package).
4. Check the conditions on the designer's Commands and Ribbons pages; WklRibbonObject().Visible("cmdX") tells you whether a command is currently shown.

• WklRibbon overview
• API reference: WklRibbon