My solution is to ask people not to go for Excel 2007.

But wait - that's not an MS approved solution!<g

I was in the beta test and people asked about just what you're asking. MS
does not want developers sticking things on the user's QAT. They want users
to add them when they want them. The MS guy got a little huffy about this
saying that if developers hacked a way to do this MS would try to thwart it.
So they're serious.

If you're a developer you're going to have to find a way to come to terms
with the ribbon. I'd forget about the QAT and learn RibbonX. I've worked
out solutions where if my app loads under pre-Excel 2007 it uses Commandbars
and if it's under 2007 it opens an XLAM with Ribbonx markup in it, that
calls back into the main app. Yeah, the complexity level has shot upward,
and maybe it's not progress but we have to learn to live with it.

--
Jim
"MrT" wrote in message
...
| The best you can do is, I believe, to settle for a 2-click access to your
| macro. You could achieve this by first adding (manually) "Menu
Commands" to
| the QAT. Then if you run a macro that adds a button to any built-in
Excel
| menu, it will automatically be added to "Menu Commnds".
|
| You're right. That's a way to do it. The problem is that I need deploy it
on
| 5000 PCs. I can't ask every one to do this manually. My solution is to ask
| people not to go for Excel 2007.
|
| Why is it now impossible (or complex) while it used to be easy to code. Is
| that progress? I beg the MS developers to add the possibility to add
custom
| buttons to the QAT.
|
| MrT
|