View Single Post
  #10   Report Post  
Posted to microsoft.public.word.docmanagement
Suzanne S. Barnhill Suzanne S. Barnhill is offline
external usenet poster
 
Posts: 33,624
Default Word 2003 docs - 'wings' - getting rid of permanently

Okay, let's back up. I agree that it would not have been possible to know
that the http://word.mvps.org/FAQs/AppErrors/MissingMenusEtc.htm article
applies to Word 2003. It was written for (IIRC) Word 2000 and has not been
updated recently, but the principles in it apply to all versions of Word
(even, I suppose, Word 2007, even though it doesn't have "menus" per se).

As for the "Idiot's Guide," it is not about *creating* macros but about how
to *install* a macro you have been given, which is your situation. Read it
carefully; it's just telling you where to paste the VBA you've been handed.
There is another article on the same subject at
http://word.mvps.org/FAQs/MacrosVBA/CreateAMacro.htm, but I think Graham's
article is clearer (though certainly not as concise). If you gave up too
early on Graham's article, you may not have reached the "Auto... macros"
section toward the end, which explains how to create the AutoNew and
AutoOpen macros he suggests creating.

--
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.

"Xylophone" wrote in message
...
Suzanne,

Many thanks. It will be frustrating for you guys. I respect and admire
what you do. I am not some geek, biting my nails in the corner. I would
have not have known from reading it that the registry article applies to
Word 2003. I shall now follow it to the letter. As for the idiot's

guide
to macros, this tells you how to create a macro. Great. What it doesn't
tell you is what to put in the macro (kindly been provided in my case).
Hence my aversion to macros: in the absence of such assistance (and where
else might I might find that?), they are totally useless to me. The same
applies to DOS. Many's the time I have been pilloried for not

understanding
DOS, yet I have never ever found any document that explains it in ordinary
language, so how am I expected to understand it? There was a little bit
about it in a Windows Manual I got many years ago. Perhaps the truth is
that you either 'get' these things or you don't. I have 4 degrees and am

a
successful person. But I tend to be literal minded, so that things of a
technical nature usually have to spelled out to me. There we go.

Suzanne S. Barnhill" wrote in message
...
The link that Stefan gave applies to all versions (with appropriate
modification of the version number in the Registry key name), and Graham
provides complete instructions on how to use his macro in the article he
referred to.

--
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.

"Xylophone" wrote in message
...
Stefan, your link makes no specific reference to Word 2003, and

Graham,
macros are a no-go area for me: incomprehensible, I'm afraid.

"Graham Mayor" wrote in message
...
Word 2003 particularly has an irriatting habit of randomly losing

some
settings from Tools Options. The easiest workaround is to force

the
settings you want in auto macros.
In this case, add the line
Options.AllowClickAndTypeMouse = False
to both an autoopen and an autonew macro in the normal template.
See http://www.gmayor.com/installing_macro.htm

--

Graham Mayor - Word MVP

My web site www.gmayor.com
Word MVP web site http://word.mvps.org



Xylophone wrote:
I use Word 2003 on a XP machine. Every time I open a new Word

doc,
I
get 'wings' attached to the cursor which drives me mad. I can get
rid of them by going into Options/Edit and unclicking Click and

Type.
But they come back when I open the next new doc, when Click and

Type
is ticked again. How can I get unclicking Click and Type to

stick,
so that this problem is solved permanently? I imagine a registry
adjustment would do the trick. Thanks.