Microsoft Office 2000/Visual Basic Programmer's Guide |
Despite sharing a common object model, each Office application stores command bar information in a different location and, in some cases, implements command bars in a different way. The primary difference is how and where each Office application stores custom command bars.
Note When you make changes to any of the built-in command bars in an Office application, information about those changes is stored in the Windows registry on a per-user basis. Information about the visibility and location of built-in and custom command bars is stored in the registry as well.
Each Office application stores its command bars either with the Office document that contains the command bars, or in an application-specific file. One important result of this is that command bars cannot be shared between Office documents of different types although they can be shared among documents of the same type. You can't create a command bar in Word and then copy that command bar to an Access application and use it there.
With the exception of Access, all Office applications store command bar information in specific locations, the path to which depends on whether user profiles have been set up for multiple users on the computer where the command bars are created. For more information about setting up user profiles, search the Microsoft Windows Help index for "user profiles."
For application-specific information about command bars, see the next five sections in this chapter.