top of page

Mysite Group

Public·33 members

Idbe Ribbon Creator

Word 2007 stripped power users of the ability to customise their menus and create toolbars. What Microsoft gave you was what you got. Your old toolbars appeared in the Developer ribbon in a pretty ugly way. The main reason was that support desks would be able to tell users what to do without hearing "that option is not in my menu." That was great for support desks but a nightmare for power users wanting to set things up for their workflow.

idbe ribbon creator

Word 2010 restored the ability for individuals to add items to a menu or ribbon and create their own ribbons. But what if you wanted to share that new ribbon with someone else? Simple, export your UI and let them import it. The problem with that was that their customisations got wiped in the process. Neat! NOT.

What I needed was the ability to give a significant number of people a specific ribbon that did not work that way and left their customisations untouched. Microsoft do give you the ability to do that using the Custom UI Editor, which is fine if you have developer level knowledge of Word. I don't. That's where Gunter Avenius' IDBE Ribbon Creator came in.

Using just its interface you have access to many built in Word commands and many icons. If that is "all" you need, it is straightforward to use, after a few attempts you can have a good looking ribbon.

If the Custom UI Editor is beyond you, this is certainly a good low cost way to create ribbons. The work I produced has been so popular that instead of being rolled out to maybe a hundred or so users in my division, it is being rolled out across the group.

I suggest now that you try a couple of other controls such as labels and then proceed to adding your new ribbon to an Access database. To avoid messing up an existing database, you should now create a brand new ACCDB format database using Access 2007.

You can now open your new Access database and have a look at what has happened. If you look a Figure 5 you will see that the database has opened with a ribbon. Choose the Reports tab and you will see the button and other controls that you set up in the first exercise. Pretty neat, but now comes the tricky bit, building a full system of menus.

At this stage, you will want to further edit your menu and here is My No. 1 tip for ribbon editing. Make regular one-hour backups of your database. My No. 2 tip is if something works, back up the database again. Why? If you get any of the XML code wrong, the database will open and the ribbon will not display. It is almost impossible to debug ribbon errors and the best way to fix it is to return to your backup to diagnose what went wrong. Okay I have made my point on backups; if you want to start editing your ribbon, you have three choices.

2) Work out the VBA code to produce your ribbon XML, this is the approach that I have taken because we have 200 menus to convert. I did find in this exercise that the XML code produced by the Ribbon Creator can be a bit long-winded and I found it easier to understand by removing quite a number of the tags in the menu XML.

3) The third option is returning to the IDBE Ribbon Creator to edit the menus. This approach is really good when you want to add new controls and need some new ribbon XML samples to help you build your ribbons. To edit a ribbon, you choose the round Application button and Open the database (see Figure 10). The Ribbon Creator then reads your current ribbon XML and displays the ribbons inside its own interface fairly accurately.

As for Ribbons, Access 2007 is now getting a bit of traction and learning how ribbons work is just one of those tasks that you need to be able to grasp if you want to call yourself a Microsoft Access specialist. Good luck because now is a great time to impress your boss.

The Ribbon Creator is a WYSIWYG interface for the development of Ribbons. The Ribbon Creator is developed in VB2005.Cklick to enlargeYou may create Tabs, Groups, Dialogbox Launcher, Labels, Buttons (large or small), ToggleButtons (large or small), Editboxes, Checkboxes, DropDown Controls and Separators.For the selection of an image for a control an appropriate dialog is available where you may also select user-defined images for a ribbon control.You have the possibility to create Screentips and Suptertips for controls supporting this feature.The created Ribbon XML can directly exported into an Access 2007 database. The callbacks needed will be imported and the required reference to "Microsoft Office 12.0 Object Library" will be set automaticly.An other options is to save a ribbon as a Word document (. docm) or as an Excel worksheet (. xlsm) while both the images chosen and the necessary callbacks will be integrated.The Ribbon XML can also saved as an XML file.

When I first started developing ribbon user interfaces, Gunter Avenius's site was invaluable. I think he still has the best collection of articles for Access ribbon developers anywhere on the internet.

This shareware/freemium option comes from the aforementioned Gunter Avenius. Based on the quality of his Access ribbon articles linked above, I'll go out on a limb and guess that this is a similarly-high quality tool.

This commercial product is specifically aimed at Excel consultants. I'm not at all familiar with its developer, but it is another available option. I assume you could use it to build a ribbon for Access, but it looks like you would need to use Excel to design and build the ribbon itself.

RibbonCreator 2016 is a WYSIWYG interface for the development of ribbons. RibbonCreator 2016 has been developed in VB2005 and requires .NET Framework 2.0.It supports creation of customised ribbons for following controls: Tabs, Groups, Labels, Buttons (large or small), ToggleButtons (large or small), Editboxes, Checkboxes, DropDown Controls, ComboBox Controls, ButtonGroups, SplitButtons (large or small), Galleries (large or small) , Menus (large or small),DynamicMenu (large or small) and Separators (in Menus also with Text).

You can select images for controls using the appropriate dialog (Office idMso internal images). Also, user-defined images for ribbon controls can be selected and written to a table within an Access database. You can create Screentips, Supertips and Keytips for controls supporting this feature.

I use custom ribbons. One for the App another for Reports etc.But when I have a SubForm with a datasheet an extra "Datasheet" ribbon occurs. That ribbon contains a lot more than I want. Like Views, Property Sheet.

Just keep in mind that when the focus moves from the "main" form, then the ribbon you specified for the sub form will become active. So, just open the sub form in design mode, and specify a ribbon for that sub form. It can be a custom ribbon, or even the same ribbon name you have for the main form.

"Do you really need ribbons"?I like them, especially when I develop in Access (or use other Office products). But for a finished App, I want to limit the possible options. I would be able to do without ribbons in most cases. But, if I understand it all right, then I must use costumized ribbons to suppress and remove the "Tell me what you want to do" option.

You cannot drag controls from one tab to another on the ribbon. If you want to move a control to another tab, you must use the Cut command to remove the control from one tab, and then paste the control on another tab. If you do cut the control and paste it, the event handler stops working. You can reconnect the event handler in the Properties window. For more information, see Properties window.

You can change the order of custom tabs on a ribbon. You can also position custom tabs before or after a built-in tab on the ribbon. For more information, see How to: Change the position of a tab on the ribbon.

The Ribbon Designer enables you to set control properties at design time by using the Properties window. In addition, the ribbon exposes a strongly typed object model that you can use to get and set the properties of Ribbon controls at run time.


Welcome to the group! You can connect with other members, ge...
bottom of page