OnCustomize event or 'not-customizable' property?

[Eric]

I have a COM add-in which adds a custom toolbar to an Outlook
Explorer, with some custom buttons on it. It works as expected, until
a user trys to "customize" the toolbar in certain ways. A user can
move the buttons around, no problem as long as they stay on my
toolbar, however if they try and move the buttons to another toolbar,
I no longer get the "OnClick" events.

I don't save the state of my toolbar or buttons when the Explorer
closes, so I'd really like to make it so the user can't customize it,
or give them a prompt when they do which tells them "don't do that
again". As soon as they close the Explorer and/or open a new one, the
new Explorer has the toolbar rebuilt and all works fine again.

I'm using the "temporary" flag to add the toolbar and all controls. I
also have the same issue with toolbars I add to inspectors. I'm
testing in Outlook 2002 right now, but I think I can recreate the same
issue in 2000 and 2003 once I reboot and try on those systems.

Thanks for any help.

 

[Ken Slovak - [MVP - Outlook]]

See if setting CommandBar.Protection to msoBarNoCustomize helps.

 

[Eric]

Thanks, I sure missed that one (though 'protection' isn't exactly what
I would have called that property).

Anyway, that took care of all the issues with my custom toolbar. Is
there anything like that for each control, or for a set of controls on
a pop-up menu item? I also added a menu option before the "Tools"
popup menu on the standard "Menu Bar" (except for in OL2000 pre SR1
because of other issues), and I don't want to lock-down customizations
to the entire standard "menu bar".

Thanks for the help!

 

[Ken Slovak - [MVP - Outlook]]

Only a CommandBar object has the Protection property.