Go Premium for a chance to win a PS4. Enter to Win


Custom Menus and Toolbars Keep Multiplying

Posted on 2009-04-14
Medium Priority
Last Modified: 2012-05-06
In an addin template in Word 2002, I've written code (Sub BuildUI)  to create a couple of custom menus and a custom toolbar with a couple of buttons. I've also written the code to delete the menus and toolbar (Sub DeleteUI). The menus, commands, and toolbar buttons are deleted with the code snippet below; the toolbar by name. (This method ensures that the controls are also deleted if the user has moved them.)

The BuildUI procedure is called from AutoExec; DeleteUI from AutoExit. DeleteUI is also called at the start of BuildUI to ensure that the custom UI is absent before it is created. I've verified through MsgBoxes that the code does run.

This method has always worked for any solution I've created. But in the environment I'm working in now, things are odd.

When I launch Word with the addin installed, Word appears with multiple copies of the toolbar. These are immediately deleted, and the custom UI recreated, but next time I launch Word, yet another copy of the toolbar is present before they are all deleted again. And so on; every time I launch Word, one more copy of the toolbar is present before it's deleted by my code.

I have verified that the toolbar(s) is/are not embedded in Normal, nor are they present in my addin. I have also verified that the CustomizationContext for my code is Normal.

Obviously, I don't want this growing number of toolbars when my users launch Word. Even though they are immediately deleted, it looks sloppy, and I'm concerned that there will come a point when Word can no longer handle this multitude of identical toolbars.
Dim ctls As Controls, ctl As Control
Set ctls = Application.CommandBars.FindControls(Tag:=MyTag)
'Controls get MyTag as tag on creation
If Not ctls Is Nothing Then 'FindControls returns Nothing if no controls with that tag
   For Each ctl In ctls
   Next ctl
End If

Open in new window

Question by:FlorisMK
  • 3
LVL 19

Expert Comment

ID: 24152565
I think I would delete them a little differently. If the Command Bar and controls are not there, then you can catch the Error and code around it. It'll through an Error 5 if the controls are not there to delete, but you can either catch that inline or build an Error Handler that will Resume Next.

Dawn Bleuel
Word MVP
With Application.CommandBars("Menu Bar")
End With

Open in new window


Author Comment

ID: 24156415
Thanks for your reaction, Dawn.

There are two objections to your approach in my situation:

1. I want to delete my custom controls wherever they may have ended up, even if the user has (accidentally) dragged them from the menu bar to somewhere else in the CommandBars collection. So that precludes explicitly referring to the Menu Bar.

2. I don't want to refer to each control by name, because it's not a robust solution and doesn't deal properly with multiple copies of the control; that's why I use the .Tag property to identify all my custom controls. Using the Tag opens up the possibility of using FindControls to delete all of them.

Accepted Solution

FlorisMK earned 0 total points
ID: 24156431
The answer turns out to be that Normal.dot is unloaded before my own addin. Therefore, the code deleting the custom UI does not affect the changes in Normal.

Author Comment

ID: 24192002
To resolve the issue and manage the toolbars more smoothly, I now use the following code:

Public Sub CreateCustomUI()
   Dim oContext As Object
   ' Store the current CustomizationContext and change it to refer
   ' to the addin template. This ensures that Normal.dot isn't
   ' contaminated with multiple copies of the UI
   Set oContext = Application.CustomizationContext
   Application.CustomizationContext = ThisDocument
   ' Delete any remaining custom UI and rebuild the custom UI 
   ' from scratch. It is essential that the UI is NOT created 
   ' with the Temporary parameter! Otherwise, the custom UI may
   ' disappear when switching between documents!
   Call DeleteCustomUI()
   Call BuildCustomUI()
   ' Make sure that the user isn't prompted to save the addin
   ThisDocument.Saved = True
   ' Restore the CustomizationContext to what it was before we
   ' started.
   Application.CustomizationContext = oContext
End Sub

Open in new window


Featured Post

Free Tool: Port Scanner

Check which ports are open to the outside world. Helps make sure that your firewall rules are working as intended.

One of a set of tools we are providing to everyone as a way of saying thank you for being a part of the community.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I'm writing to share my clumsy experience in using this elegant tool so you can avoid every stupid mistake I made. (I leave it to the authorities to decide if this deserves a place in the Knowledge archives.)  Now that I am on the other side of my l…
This article describes a method of delivering Word templates for use in merging Access data to Word documents, that requires no computer knowledge on the part of the recipient -- the templates are saved in table fields, and are extracted and install…
Learn how to create and modify your own paragraph styles in Microsoft Word. This can be helpful when wanting to make consistently referenced styles throughout a document or template.
Office 365 is currently available in five editions. Three of them are for business use: Office 365 Business Essentials, Office 365 Business, and Office 365 Business Premium. Two of them are for home/personal use: Office 365 Home and Office 365 Perso…

972 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question