Share via

KeyBindings problem (Word 2011 & 2016 Mac)

Anonymous
2016-04-08T11:03:45+00:00

Hi All,

Generally KeyBindings seems to work. For example I can use something like the following:

KeyBindings.Add wdKeyCategoryMacro, "mySub", BuildKeyCode(Asc("A"))

Now mySub is called each time I press the "A" key on the keyboard. Great! But when I do exactly the same with 4 special characters from the German keyboard layout I get an error message telling me something like "Runtime error 5346, Word cannot change this keys function." (translated from German). The 4 characters that I need the KeyBindings for are "ß, Ä, Ö, Ü" (Umlauts):

KeyBindings.Add wdKeyCategoryMacro, "mySub", BuildKeyCode(Asc("ä"))

Very strange: This worked before with Word 2011; and I think 2016 as well. But since one of the recent updates I can't get it to run any more. I don't know with which version it was running before because I haven't used for a while.

Any idea appreciated!

Greetings from Germany

Microsoft 365 and Office | Word | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

2 answers

Sort by: Most helpful
  1. Anonymous
    2016-04-09T15:59:55+00:00

    I'm facing this problem since a few weeks. Can't tell exactly because the object is a piece of software that I don't touch very often. I 1st got this information from my customers.

    Word 2011 is 14.6.2 and 2016 is 15.20.0.

    Sorry, I guess I can't go back far enough because only very few versions of Office are saved. I'll try anyway. But could you please tell me in what way this should help.

    Thanks!

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2016-04-09T09:05:04+00:00

    From when are you facing this problem?

    What is the version number of office 2016?

    Revert to the previous version through time machine and get to know in which version this works.

    Was this answer helpful?

    0 comments No comments