ISSUE: when users create pdf documents based on customized word templates the dialog box appears with the following message: "The macros in this project are disabled.  Please refer to the online help or documentation of th ehost application to determine how to enable macros."

(1) The errors only happen to *.docx files created from upgraded customized Word 2007 templates (*.doctm).  The templates had been created in Word 2003 (*.dot)

(2) We use Adobe Acrobat X Pro as well as PDF Nuance create to create pdf documents.

(3) All of the templates are located in a trusted location.  All macros are enabled.  These settings have been checked and confirmed.

  I am able to create and save the document.  However when I create a PDF document, it gives me the error.  It appears as though everything works as it supposed to, including creation of the PDF document, but it pops up with the error.  If I take a document that was not created via the templates and create a PDF file, that works fine.

Hi,

Please create a new template from Word 2007 test if it works.

If it works fine, the problem probably causes by the template had been created in Word 2003.

As my experience, such as Adobe PDFMaker Add-in performs a version check to verify that the version of Microsoft Office that is being used is Microsoft Office 2003. Therefore, the Adobe PDFMaker Add-in cannot be installed in 2007 Office programs.

Best regards.

Hi William,

FWIW, I think this problem continues even with the latest version of Acrobat and Word 2010.  When Acrobat is allowed to embed itself virally into Word, everytime it's used, template macros get disabled and you have to restart your instance of Word. 

We have this happening in our Office and I haven't yet had time to try and figure out what exactly is happening or even if it's possible with Adobe's latest version of Acrobat to do a Custom Install and bypass the viral add-in approach they favor.  That was possible on former versions, but again, I'm not sure if that's still an option.  So for now after creating a PDF with Acrobat, our staff closes out of Word completely and restarts a new instance of Word. 

Hi Rich Michaels,

Thank you for sharing your  experience here. It will be very beneficial for other community members who have similar questions.

Best regards.

These templates were recreated by a Microsoft certified consultant company for Word 2007.

We do not know why, but it is NOT only the Adobe PDF maker, but also other packages such as PDF Nuance.

The templates that were created in Word 2003 actually never had any errors when you went to create the pdf.

So, this is not the issue.

Hi Rich,

The error pops up when you open Adobe > choose create PDF > choose the saved *.docx file created from the 2007 template.  This same error posp up with other PDF creator applications.  The issue is in Word 2007 template.  So, regardless if the file is pdf while word is open or not, the error still appears.   

You can turn off disabling macros using this registry entry:

 

HKEY_CURRENT_USER\Software\Adobe\Acrobat\PDFMaker\10.0\Word\Settings\DisableMacro (set to 0)

 

If DisableMacro does not exist, add it as a "DWORD Value".

 

Note, that disabling macros after an acrobat conversion is intentional to prevent a malicious document from running a macro without your consent. Keep that in mind when making this change.

 

See more here: https://helpx.adobe.com/acrobat/kb/known-issues-acrobat-x-reader.html#main_Word_PDFMaker

• Edited by John Wynne 11 hours 10 minutes ago

You can turn off disabling macros using this registry entry:

 

HKEY_CURRENT_USER\Software\Adobe\Acrobat\PDFMaker\10.0\Word\Settings\DisableMacro (set to 0)

 

If DisableMacro does not exist, add it as a "DWORD Value".

 

Note, that disabling macros after an acrobat conversion is intentional to prevent a malicious document from running a macro without your consent. Keep that in mind when making this change.

 

See more here: https://helpx.adobe.com/acrobat/kb/known-issues-acrobat-x-reader.html#main_Word_PDFMaker

• Edited by John Wynne Friday, September 04, 2015 8:23 PM