Problem with mail editor Word instance

[Bo Hansson]

The primary user interface in my Word 2003 VBA application (running in
XP-environment) is an extension added to Words menu bar. The Customization
Context is set to NomalTemplate.

Problems occur when Word is used as the Outlook Editor. If the user (after
computer booting) starts with mail editing, the menu works OK in the mail
editor Word instance. However, if the user then adds another instance by
clicking on the Word application icon, my added menu does not work.

Any ideas of a work around ?

/Bosse H

 

[Word Heretic]

G'day "Bo Hansson" <[email protected]>,

Many problems occur when you use Word as an email editor. Don't

Steve Hudson - Word Heretic

steve from wordheretic.com (Email replies require payment)
Without prejudice


Bo Hansson reckoned:

 

[Helmut Weber]

Hi Bo,

one could think of this or of that.
All workarounds I've heard of will cause
other problems, possibly more severe,
however sophisticated they may be.
Or probably because they are.

If your client refuses
to abandon Word as EMail-Editor,
I'd create a button "go", or "start".
One mouseclick more for the user,
if he can think of it. :-/

Greetings from Bavaria, Germany

Helmut Weber, MVP
"red.sys" & chr(64) & "t-online.de"
Word XP, Win 98
http://word.mvps.org/

 

[Tom Winter]

A quick thought here. Go back to the "old" way of doing menu items. I assume
you are capturing the click event of the commandbarbuttons. Instead, go back
to the way Word 97 did it and set the OnAction (I believe) property of the
buttons to a publicly visible macro. Have that macro call the appropriate
code in your add-in.

Don't really know if this would help with the WordMail problem, but it's a
thought!

One other thought, if you are using the click events. Make sure you set the
..Tag property of the buttons to a unique value. In Word at least, the event
raising is based on the Tag property. (Sorry, I know I'm not explaining that
very well...)