[Cindy M.]

Hi Tom,

Hope I catch all your points, below...

I get a nice little Microsoft Word dialog box with an OK button - and
nothing else.

Hmmm. Confirms what you see in the dialog box. Interesting. See if this
macro (5 lines) works to REMOVE that odd assignment:

Sub RemoveKeyboardAssignment()
Application.CustomizationContext = NormalTemplate
Application.KeyBindings.Key( _
KeyCode:=BuildKeyCode(wdKeyShift, wdKeyF11)).Clear
End Sub

I get "the key combination has not been reassigned"

when I rurn GetKeyboardAssignment now.

I'm a little confused here - what exactly have we proven? That Shift-F11
had some weird procedure associated with it?

OK, if I'm following correctly: Yesterday we had an assignment with no
discernible name (the message box and dialog box both showed nothing). You
ran the macro, above. Then you tested my first macro again and get the
message the shortcut isn't assigned.

This means that something, at some unknown time, managed to assign the
keyboard shortcut to a command with no name. I've never heard of this
happening and I'd have bet it wasn't possible :-), but I guess I'd have lost
that bet. OR there was some glitch in Word where an assignment was made and
lost at some point. Impossible to know, at this remove. The important thing
is that we were able to remove it.

I've only recently begun to understand how macros work in Word. I don't
mean the macros themselves, but how they're stored and what macro is
available in what place(s).

All of these assignments I've been playing with I've been storing into
document templates specifically for the client whose work I'm doing at the
time.

Understood. I may be repeating something you already know, but:

Word has a hierarchy for toolbar, menu and keyboard assignments. In case of
conflict, the active document has priority and will override what's assigned
in its attached template. Attached template has priority over anything in any
global template. Individual global templates override Normal.dot (among the
global templates, the last to be loaded has priority). So I do find it
unusual that an assignment in Normal.dot (that's the only thing my macros
should have affected) would override your individual templates.

If you've ever done transcription, you'll know that there are times when
speakers appear to be talking in some unknown language.

Once. As part of an administrative job many years ago. To add to the horror
g, it was an international meeting with many languages. You can appreciate,
I'm sure!

When that happens,
I'll put the italicized text "[undecipherable]" into the document, bound to
the F11 key. Some clients want included as well an indication of location
in the file or tape where these unclear passages occur, and for that I use
Shift-F11 to insert the same text, followed by the manual insertion of the
appropriate information (elapsed time into the digital file or counter
position on the trascribing machine). I have no need for these functions in
my own work so I don't store them in Normal.dot.

Since running your RemoveKeyboardAssignment macro, I'm no longer seeing
Shift-F11 execute anything other than what I want, when I want, so the
initial problem that prompted this thread is solved.

Excellent :-)!

I'm still somewhat fuzzy on how Word actually handles macros. I've had
cases where I've recorded a macro bound to a hotkey and had that hotkey do
nothing, but then I could exit and restart Word, and voila! the hotkey now
works.

Count yourself fortunate :-) I had one installation that - for a while -
recognized NO assigned keyboard shortcuts. Then all of a sudden, they were
all back. No idea what was going on and nothing I tried could change it. I've
seen similar complaints maybe once every couple of years, here on the groups.
A total mystery...

Getting back to my original question for a moment - I finally figured out
what you were talking about when you provided code for reprogramming the F1
key. Am I correct in assuming that, as written, the macro would have to be
manually executed at the start of each Word session, after having the name
of the macro to be called with the F1 key inserted into the appropriate
line of the code (I called it MakeF1)?

If you wanted to change the macro assignment, yes, you'd need to run it each
time you need a different macro.

However, I'd tend to go the path of least resistence: Keep all the macros in
one "pot" and just rename the one I need at the moment. Then I wouldn't need
to keep changing the F1 assignment.

The macro could easily be adjusted to change the Normal.dot, or the template
attached to the active file. Whatever would be most appropriate for your
circumstances. Since you say you keep a template for each client, what might
work best for you would be

1. Open the template

2. In the VB Editor, insert a module into the template and put the macro you
need for that template in it.

3. Make sure the template is the active window in Word

4. Run the macro as it stands (substituting the name of the macro as
appropriate for the template).

5. This should save the keyboard shortcut in the template.

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Jun 17 2005)
http://www.word.mvps.org

This reply is posted in the Newsgroup; please post any follow question or
reply in the newsgroup and not by e-mail :-)