Word 2003 Macros in project are disabled

[Ginna]

Hi, I need assistance in distributing macros in Word 2003 macros. We are currently running Win2000/Word 2000 and loading a Word startup template from this folder: C:\Program Files\Microsoft Office\Office\Startup. Macro security is set to High, Trust all installed add-ins and templates is checked, and the Startup location specified in Tools, Options, File Locations is the default location. All is running fine under this configuration

In planning the migration to Word 2003, I reviewed the MSKB article 827890 that states: "Word 2003 automatically loads any document template (*.dot) or Word add-in library (*.wll) that is saved in either of two Startup folders. One of these Startup folders is in the folder that contains the Microsoft Office 2003 program files. The other is in the folder that contains the Microsoft Windows operating system files, or the folder that contains the user's profile on computers with user profiles enabled.

So, on an XP/Word 2003 machine I copied the macro file to C:\Program Files\Microsoft Office\Office11\Startup. Macro security is on High and trust installed templates is checked. However, when I start Word 2003 I get this error message: "The macros in this project are disabled." I don't get the error message when I copy the template to C:\Documents and Settings\username\Application Data\Microsoft Word\Startup

Based on the above mentioned KB article, I assumed the macros would load if stored in the Program Files...Startup folder. Please help me understand what is happening. Do I now need to digitally sign the macros in order for them to be enabled when starting from the Program Files...Startup folder? There are some system administrators in my company who prefer to load macros from Program Files...Startup instead of from the user profile location

By the way, what is the best approach to distributing macros in Word 2003

Thanks for any advice you can provide

Ginna

 

[Cindy M -WordMVP-]

Hi =?Utf-8?B?R2lubmE=?=,

So, on an XP/Word 2003 machine I copied the macro file to C:\Program Files\Microsoft

Office\Office11\Startup. Macro security is on High and trust installed templates is
checked. However, when I start Word 2003 I get this error message: "The macros in
this project are disabled." I don't get the error message when I copy the template to
C:\Documents and Settings\username\Application Data\Microsoft Word\Startup.I've never seen the article. But I know that the Office STARTUP folder is *not* trusted
for what you describe. You need the WORD Startup folder (and that can be set via File
locations, same as you know from Word 2000).

Cindy Meister
INTER-Solutions, Switzerland
http://homepage.swissonline.ch/cindymeister (last update Sep 30 2003)
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

 

[Peter Huang]

Hi Ginna,

As the KB article 827890 said,
Earlier versions of Word trusted all add-in files in either of these
Startup folders if the Trust all installed add-ins and templates check box
was selected in the Security dialog box. Word 2003 only trusts one folder,
and that folder is specified in the Options dialog box on the File
locations tab as the Startup path.

We will know that in Word 2003, it will only trusts only one folder, also
we can specified the folder by browsing to Tools, Options, File Locations.

Best regards,

Peter Huang
Microsoft Online Partner Support

Get Secure! - www.microsoft.com/security
This posting is provided "AS IS" with no warranties, and confers no rights.

 

[Ginna]

Thank you for the clarification. I was confused why Word 2003 would automatically load a template from the Office Startup folder if it does not trust the folder. I imagine there could be business or technical reasons to load a template from that folder, I just don't know (from lack of experience) what those situations could be. However, I do accept that Word 2003 only trusts the Word Startup folder (under the user's profile)

Thanks again to both Peter and Cindy.