|
|
Our Hot Pick: Rising Antivirus 2006 - Certified by TUV & Checkmark! Get 10% discount by entering this coupon code: ONDISCOUNT10
I don't think this is unique to Word 2003 (I noticed the same thing in Word
2000) - but why can't the F1 key be used for a macro instead of to bring up
Help? Does anyone know - or IS there in fact a way to assign F1 to execute
a macro?
Tom
--
remove .spoo to reply by email
|
|
Hi Tom,
[Quoted Text] > I don't think this is unique to Word 2003 (I noticed the same thing in Word
> 2000) - but why can't the F1 key be used for a macro instead of to bring up
> Help? Does anyone know - or IS there in fact a way to assign F1 to execute
> a macro?
>
There is, but it requires a macro. The basic code is as follows. Note the
CustomizationContext: you need to set this to where you want the assignment
to be valid. "TestWord" is the name of the macro.
Application.CustomizationContext = ActiveDocument
Application.KeyBindings.Add wdKeyCategoryMacro, "TestWord", wdKeyF1
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 :-)
|
|
On Fri, 22 Sep 2006 11:21:47 +0200, Cindy M. <C.Meister-C[ at ]hispeed.ch>
wrote:
[Quoted Text] >> I don't think this is unique to Word 2003 (I noticed the same thing in Word
>> 2000) - but why can't the F1 key be used for a macro instead of to bring up
>> Help? Does anyone know - or IS there in fact a way to assign F1 to execute
>> a macro?
>>
>There is, but it requires a macro. The basic code is as follows. Note the
>CustomizationContext: you need to set this to where you want the assignment
>to be valid.
I want the assignment to be globally available to all documents and
templates.
> "TestWord" is the name of the macro.
>
> Application.CustomizationContext = ActiveDocument
> Application.KeyBindings.Add wdKeyCategoryMacro, "TestWord", wdKeyF1
I opened normal.dot, created a macro called Autoexec, and copied your code
into that macro.
When I ran the autoexec manually, I got the following:
Run-time error 5346
Word cannot change the function of the specified key.
I then closed Word and restarted it. Now every time I open word, I get the
following:
Run-time error 4248
This command is not available because no document is open.
I then created a macro called "TestWord" and copied your code into that
macro. I then ran the macro and got no errors.
I started to record a macro, but Word would still not let me use the F1
key.
Color me confused,
Tom
--
remove .spoo to reply by email
|
|
Hi Tom,
[Quoted Text] > >> I don't think this is unique to Word 2003 (I noticed the same thing in Word
> >> 2000) - but why can't the F1 key be used for a macro instead of to bring up
> >> Help? Does anyone know - or IS there in fact a way to assign F1 to execute
> >> a macro?
> >>
> >There is, but it requires a macro. The basic code is as follows. Note the
> >CustomizationContext: you need to set this to where you want the assignment
> >to be valid.
>
> I want the assignment to be globally available to all documents and
> templates.
>
> > "TestWord" is the name of the macro.
> >
> > Application.CustomizationContext = ActiveDocument
> > Application.KeyBindings.Add wdKeyCategoryMacro, "TestWord", wdKeyF1
>
> I opened normal.dot, created a macro called Autoexec, and copied your code
> into that macro.
>
> When I ran the autoexec manually, I got the following:
>
> Run-time error 5346
> Word cannot change the function of the specified key.
>
>
> I then closed Word and restarted it. Now every time I open word, I get the
> following:
>
> Run-time error 4248
> This command is not available because no document is open.
>
> I then created a macro called "TestWord" and copied your code into that
> macro. I then ran the macro and got no errors.
>
> I started to record a macro, but Word would still not let me use the F1
> key.
>
> Color me confused,
>
First, you need to create the macro to which you want to assign the keyboard
shortcut. Make sure it's in Normal.dot Then you put that macro name in place of
TestWord.
Replace ActiveDocument with: NormalTemplate
Now make sure the insertion point is blinking in the "Sub" and press F5 to
execute it. You only need to run it the one time. After that, F1 will always
execute the macro (until you loose Normal.dot, anyway).
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 :-)
|
|
On Mon, 25 Sep 2006 18:20:05 +0200, Cindy M. <C.Meister-C[ at ]hispeed.ch>
wrote:
[Quoted Text] >Hi Tom,
>
>> Color me confused,
>>
>First, you need to create the macro to which you want to assign the keyboard
>shortcut. Make sure it's in Normal.dot Then you put that macro name in place of
>TestWord.
I am a transcriptionist, and clients have different ways of how they want
their transcripts to work.
In general, I want to use F1 to designate either the interviewer in a
one-on-one interview, or the moderator if it's a focus group, so the actual
content of the F1 macro will change from client to client. One client may
want "Q:{tab}", another may want I:{tab}, and so on.
>Replace ActiveDocument with: NormalTemplate
You've lost me here. What am I doing and how do I do it?
Please realize that I know virtually nothing about visual basic (which is
what I assume you're talking about here)
>Now make sure the insertion point is blinking in the "Sub" and press F5 to
>execute it. You only need to run it the one time. After that, F1 will always
>execute the macro (until you loose Normal.dot, anyway).
I'm sorry, but I still don't understand you. I'm confused in that I don't
know if you're talking about the macro code you provided in your original
message, or if you're telling me that I have to write the macro that I
actually want to use with the F1 key.
I've tried a few variations on what I *THOUGHT* you were talking about, but
once again I run into the run-time error that tells me the F1 key cannot be
reprogrammed.
This is making me crazy....
Tom
--
remove .spoo to reply by email
|
|
Hi Tom,
[Quoted Text] > I'm sorry, but I still don't understand you.
>
In that case, I think it would be best if you do NOT try to
reprogram the F1 key. When you poke that deeply into things
that aren't meant to be changed, you have to understand
what you're doing, and how to correct any problems that
might crop up. F1 is dedicated across all Windows apps to
calling up Help, which is why it's locked down so tightly.
There are so many other keyboard combinations available, it
would be best to use one of them, even if, at the moment,
you don't think it will be as "comfortable" to use as F1.
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
:-)
|
|
On Tue, 26 Sep 2006 18:24:46 +0200, Cindy M. <C.Meister-C[ at ]hispeed.ch>
wrote:
[Quoted Text] >Hi Tom,
>
>> I'm sorry, but I still don't understand you.
>>
>In that case, I think it would be best if you do NOT try to
>reprogram the F1 key. When you poke that deeply into things
>that aren't meant to be changed, you have to understand
>what you're doing, and how to correct any problems that
>might crop up. F1 is dedicated across all Windows apps to
>calling up Help, which is why it's locked down so tightly.
After reading your lecture above, and given the presence of "newusers" in
this group's title, I am left wondering why you bothered replying in the
first place. If F1 is locked down so securely, then why not just say "you
can't do that unless you know VBA" and left it at that?
I cheerfully admit that I am not a programmer, but my original question was
a simple one, and if you weren't prepared to provide this "new user" with
meaningful assistance, then why even bother to reply?
Leaving someone with the impression that they're an idiot leaves me
fervently hoping that you are not in HR... :-)
Tom
--
remove .spoo to reply by email
|
|
You are trying to do something that you cannot do. You came here for help
and you have been given EXPERT help in very simple terms. You still cannot
do it. You received $500 consultancy for free and now you are criticising.
I suggest that you apologise for outright effrontery.
--
Terry Farrell - Word MVP
http://word.mvps.org/
"Tom Hall" <aria1946[ at ]gmail.com.spoo> wrote in message
news:hg2lh2t90574sptvmtham0gjlhql7a8ao2[ at ]4ax.com...
[Quoted Text] > On Tue, 26 Sep 2006 18:24:46 +0200, Cindy M. <C.Meister-C[ at ]hispeed.ch>
> wrote:
>
>>Hi Tom,
>>
>>> I'm sorry, but I still don't understand you.
>>>
>>In that case, I think it would be best if you do NOT try to
>>reprogram the F1 key. When you poke that deeply into things
>>that aren't meant to be changed, you have to understand
>>what you're doing, and how to correct any problems that
>>might crop up. F1 is dedicated across all Windows apps to
>>calling up Help, which is why it's locked down so tightly.
>
> After reading your lecture above, and given the presence of "newusers" in
> this group's title, I am left wondering why you bothered replying in the
> first place. If F1 is locked down so securely, then why not just say "you
> can't do that unless you know VBA" and left it at that?
>
> I cheerfully admit that I am not a programmer, but my original question
> was
> a simple one, and if you weren't prepared to provide this "new user" with
> meaningful assistance, then why even bother to reply?
>
> Leaving someone with the impression that they're an idiot leaves me
> fervently hoping that you are not in HR... :-)
>
>
> Tom
>
> --
> remove .spoo to reply by email
|
|
I think you're being a bit hard here TF. This poster is obviously confused
and distressed and perhaps a few allowances can be made. But I agree with
you that services on the NG from experts like yourself are very valuable to
the user. A darned sight better than the so called 'help' centres in the
Philippines or India!
"TF" <terryfarrell%40%6d%73%6e%2ecom> wrote in message
news:e7qFw4k4GHA.4976[ at ]TK2MSFTNGP06.phx.gbl...
[Quoted Text] > You are trying to do something that you cannot do. You came here for help > and you have been given EXPERT help in very simple terms. You still cannot > do it. You received $500 consultancy for free and now you are criticising. > > I suggest that you apologise for outright effrontery. > > -- > Terry Farrell - Word MVP > http://word.mvps.org/> > > "Tom Hall" <aria1946[ at ]gmail.com.spoo> wrote in message > news:hg2lh2t90574sptvmtham0gjlhql7a8ao2[ at ]4ax.com... >> On Tue, 26 Sep 2006 18:24:46 +0200, Cindy M. <C.Meister-C[ at ]hispeed.ch> >> wrote: >> >>>Hi Tom, >>> >>>> I'm sorry, but I still don't understand you. >>>> >>>In that case, I think it would be best if you do NOT try to >>>reprogram the F1 key. When you poke that deeply into things >>>that aren't meant to be changed, you have to understand >>>what you're doing, and how to correct any problems that >>>might crop up. F1 is dedicated across all Windows apps to >>>calling up Help, which is why it's locked down so tightly. >> >> After reading your lecture above, and given the presence of "newusers" in >> this group's title, I am left wondering why you bothered replying in the >> first place. If F1 is locked down so securely, then why not just say "you >> can't do that unless you know VBA" and left it at that? >> >> I cheerfully admit that I am not a programmer, but my original question >> was >> a simple one, and if you weren't prepared to provide this "new user" with >> meaningful assistance, then why even bother to reply? >> >> Leaving someone with the impression that they're an idiot leaves me >> fervently hoping that you are not in HR... :-) >> >> >> Tom >> >> -- >> remove .spoo to reply by email > >
|
|
Hi Tom,
[Quoted Text] > After reading your lecture above, and given the presence of "newusers" in
> this group's title, I am left wondering why you bothered replying in the
> first place. If F1 is locked down so securely, then why not just say "you
> can't do that unless you know VBA" and left it at that?
>
> I cheerfully admit that I am not a programmer, but my original question was
> a simple one, and if you weren't prepared to provide this "new user" with
> meaningful assistance, then why even bother to reply?
>
> Leaving someone with the impression that they're an idiot leaves me
> fervently hoping that you are not in HR... :-)
>
We get all levels of user in this group. From absolute first-time at the
computer keyboard, through first time with Word, all the way to C++ developer
wanting help with code - and every imaginable variation within this spectrum.
It's impossible to evaluate a person's capabilities based on a couple of
short messages :-)
I wasn't implying you're an idiot - but you said yourself that you haven't
the background to understand what I gave you. At that point, I have to make a
judgement call whether I'll potentially be causing more harm by following
through with you to the bitter end (you make the change) with the result that
somewhere down the line your system becomes "unusable".
What you want to do is possible (I tested the code before I posted it here),
but it means doing something the average user isn't supposed to do. And when
you step beyond the "safety boundaries" - whether using code, working on a
construction site, or doing anything else - a basic understanding of what
you're doing and the consequenses and dangers involved is required. Based on
your reaction, I consider it better not to take the chance of wrecking your
installation that could result in the loss of customizations (macros,
keyboard assignments, toolbars) you use in your daily work.
If there weren't any alternatives for solving the problem (executing a macro
with a keyboard shortcut), then I would have continued to work on the problem
with you. But given there are hundreds of possible keyboard combinations, the
risk of causing you damage was too high compared to the gain.
And no, I'm certainly not in HR, nor would I ever care to be. I'm a lousy
nurse / handholder and am quite aware of it :-) My strength is in looking at
problems and seeing possible solutions, with a general disregard of any
emotions or feelings involved.
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 :-)
|
|
On Thu, 28 Sep 2006 11:55:38 +0200, Cindy M. <C.Meister-C[ at ]hispeed.ch>
wrote:
[Quoted Text] >Hi Tom,
>If there weren't any alternatives for solving the problem (executing a macro
>with a keyboard shortcut), then I would have continued to work on the problem
>with you. But given there are hundreds of possible keyboard combinations, the
>risk of causing you damage was too high compared to the gain.
Thank you for the information. You were certainly a lot more forthcoming
than Microsoft when I went to them with this problem. They didn't even
allude to the possibility of doing it at all.
>And no, I'm certainly not in HR, nor would I ever care to be. I'm a lousy
>nurse / handholder and am quite aware of it :-) My strength is in looking at
>problems and seeing possible solutions, with a general disregard of any
>emotions or feelings involved.
Then I apologize for my earlier statement. I've implemented a third-party
solution using a program which will cheerfully redefine just about any key
on the keyboard and can be made to act on specific applications only. F1 is
certainly universally recognized as a help function in Windows.
Sorry for ruffling some feathers here, and I'm glad yours weren't among
them. :-)
Tom
--
remove .spoo to reply by email
|
|
Hi Tom,
[Quoted Text] > I've implemented a third-party
> solution using a program which will cheerfully redefine just about any
key
> on the keyboard and can be made to act on specific applications only.
>
Glad you've found a solution :-)
> Sorry for ruffling some feathers here, and I'm glad yours weren't among
> them. :-)
>
All kinds of people drop in here, some of whom can be very unreasonable.
So the regulars tend to watch out for one another. Terry happens to be a
good friend, as was just trying to protect me :-)
-- Cindy Meister
|
|
On Fri, 29 Sep 2006 13:40:19 +0200, Cindy M. <C.Meister-C[ at ]hispeed.ch>
wrote:
[Quoted Text] >Hi Tom,
>
>> I've implemented a third-party
>> solution using a program which will cheerfully redefine just about any
>key
>> on the keyboard and can be made to act on specific applications only.
>>
>Glad you've found a solution :-)
It seems there is no end to the mysteries of Word. Right now I'm trying to
figure out why a macro I just wrote which does nothing but type some
formatted text into a document is triggered with the Shift-F11 key even
when I don't assign the macro to either a key or to a menu. If I add a
hotkey, (e.g. F11), then BOTH F11 and Shift-F11 trigger the macro. If I
delete the macro, Shift-F11 does nothing. If I manually create the macro
from scratch avoiding any key assignment, Shift-F11 will again trigger the
macro. Very strange.
Tom
--
remove .spoo to reply by email
|
|
By default, Shift+F11 is assigned to "Go to the previous field."
--
Suzanne S. Barnhill
Microsoft MVP (Word)
Words into Type
Fairhope, Alabama USA
Word MVP FAQ site: http://word.mvps.org
Email cannot be acknowledged; please post all follow-ups to the newsgroup so
all may benefit.
"Tom Hall" <aria1946[ at ]gmail.com.spoo> wrote in message
news:60bqh2tncgec6t7ck26sqsv7aef23s7nfd[ at ]4ax.com...
[Quoted Text] > On Fri, 29 Sep 2006 13:40:19 +0200, Cindy M. <C.Meister-C[ at ]hispeed.ch>
> wrote:
>
> >Hi Tom,
> >
> >> I've implemented a third-party
> >> solution using a program which will cheerfully redefine just about any
> >key
> >> on the keyboard and can be made to act on specific applications only.
> >>
> >Glad you've found a solution :-)
>
> It seems there is no end to the mysteries of Word. Right now I'm trying to
> figure out why a macro I just wrote which does nothing but type some
> formatted text into a document is triggered with the Shift-F11 key even
> when I don't assign the macro to either a key or to a menu. If I add a
> hotkey, (e.g. F11), then BOTH F11 and Shift-F11 trigger the macro. If I
> delete the macro, Shift-F11 does nothing. If I manually create the macro
> from scratch avoiding any key assignment, Shift-F11 will again trigger the
> macro. Very strange.
>
>
>
> Tom
>
> --
> remove .spoo to reply by email
|
|
|