View Single Post
  #2   Report Post  
Posted to microsoft.public.word.mailmerge.fields
Graham Mayor Graham Mayor is offline
external usenet poster
 
Posts: 19,312
Default Registry patch to lower security of word - Word does not respond

NO! NO! NO!
Do *NOT* set the security of your users PCs to low. This will open the door
to macro viruses and is not necessary for what you want to achieve.
You need to set the user's PCs to trust installed templates and add-ins.
This (and the macro security) is set from the Word data key settings sub key
along with a load of other settings. This binary key does not lend itself to
manual manipulation in the manner you imagine.
You are either going to have to instruct the users how to set macro security
to trust installed templates and add-ins, or do what the company is paying
you for and adjust each one yourself.

--

Graham Mayor - Word MVP

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


Dixie wrote:
I need to change the security of Word 2003 to allow it to enable
macros in templates in a large site with dozens of computers. Every
computer has Word's default security set to high. I have come up
with this registry patch.
------------------------------------------------------------------------------
Windows Registry Editor Version 5.00

[HKEY_CURRENT_USER\Software\Microsoft\Office\11.0\W ord\Security]
"Level"=dword:00000001
------------------------------------------------------------------------------
I found the key by watching what key changed in the registry when I
lowered the security of Word manually. Now I am really perplexed. If I
run this registry patch, it changes the key shown from 3 (high)
to 1 (low), just as doing it manually via Word does. However, when
you go back into Word, the Security is still set to high, even though
the Level is set to 1 in the registry. Surely I am missing something
here. The registry key responds to changing the macro security in
Word, but Word does not respond to having the key changed from
outside.
Can anyone please help with this, as this key is on
HKEY_CURRENT_USER, which means in the network environment it is in,
it has to be done once for each person using each workstation. This
is a very large manual task.
TIA
dixie