Hi Don H.

I will try a few things this weekend to avoid this problem


--

Regards Ron de Bruin
http://www.rondebruin.nl/tips.htm


"donh" wrote in message ...
Hi Ron,
Thank you, it's kind of you to help, but I had already looked at that code,
and unfortunately it doesn't answer my question. The example code uses the
module-level variable 'Rib" to access the ribbon, having set that variable in
the onLoad callback. Sometimes things go wrong in macros (yes, I know, they
shouldn't...but they do) and if there is any error, even in a macro that has
nothing to do with ribbons, the variable Rib gets set back to Nothing, at
which point there's no way to find the Ribbon objects again.

My question is whether there is any independent way for VB code to navigate
to the Ribbon objects, perhaps starting with the Application object (or any
other always-accessible place)? I would like my module to be essentially
"stateless" and not depend on that global variable remaining set. In the
pre-ribbon days, one could navigate from the Application.CommandBars property
and find all the menu objects. This doesn't appear to work the same way for
ribbons, and I'm looking for the comparable technique.
--
Don H.