Prev: PRINTDATE Field Calculation
Next: I want to catch the "Save on Exit" routine
From: Jon Borel on 27 Apr 2010 12:22
Hello,

We just upgraded our XP boxes to Word 2007 (SP2) with Acrobat PDFMaker
(Reader 9.3.1) as a COM Addin.

When we PDF one of our Word Docs (that contains Macros), we can no longer
run macros in that document (Word Error: "The macro cannot be found or has
been disabled because of your Macro security settings," or "The macros in
this project are disabled.") The macros again work perfectly after we close
and then reopen the affected document.

Trust Center Macro Security is set to "Enable all."

My problem sounds exactly like one I found here:
http://www.acrobatusers.com/forums/aucbb/viewtopic.php?id=16724

Any ideas?

Thanks,
Jon



From: Jon Borel on 27 Apr 2010 12:48
A little more info: Although I can't run my macros until I close and then
reopen the document, Word's built-in macros seem to run fine (signs point to
my macros). Also, a very simple "HelloWorld" macro continues to run after PDF
(more signs point to my macros). I am running an application event procedure
(SelectionChange)...

"Jon Borel" wrote:

> Hello,
>
> We just upgraded our XP boxes to Word 2007 (SP2) with Acrobat PDFMaker
> (Reader 9.3.1) as a COM Addin.
>
> When we PDF one of our Word Docs (that contains Macros), we can no longer
> run macros in that document (Word Error: "The macro cannot be found or has
> been disabled because of your Macro security settings," or "The macros in
> this project are disabled.") The macros again work perfectly after we close
> and then reopen the affected document.
>
> Trust Center Macro Security is set to "Enable all."
>
> My problem sounds exactly like one I found here:
> http://www.acrobatusers.com/forums/aucbb/viewtopic.php?id=16724
>
> Any ideas?
>
> Thanks,
> Jon
>
>
>
From: Fumei2 via OfficeKB.com on 27 Apr 2010 15:48
As a suggestion, do NOT keep the Adobe add-ins loaded. I do not. I have a
icon on the toolbar that:

1. loads the Adobe PDFMaker add-in
2. makes the PDF of the ActiveDocument
3. UNLOADS the PDFMaker add-in.

The issue, as far as I can see, is that the .dot file of PDFMaker is
generally kept loaded. It is in Startup. Bad idea. Frankly, I do not allow
ANY add-in to be a permanent one.

Jon Borel wrote:
>A little more info: Although I can't run my macros until I close and then
>reopen the document, Word's built-in macros seem to run fine (signs point to
>my macros). Also, a very simple "HelloWorld" macro continues to run after PDF
>(more signs point to my macros). I am running an application event procedure
>(SelectionChange)...
>
>> Hello,
>>
>[quoted text clipped - 16 lines]
>> Thanks,
>> Jon

--
Gerry

Message posted via http://www.officekb.com

From: Graham Mayor on 28 Apr 2010 02:25
Acrobat 9 does not use a DOT add-in in the startup folder? Dot add-ins for
Acrobat have not been used since Acrobat 6 (which is not compatible with
Word 2007). Unloading the add-in by macro should not in any case be
necessary. In fact until Adobe fixes this problem (if indeed it is a known
problem) it might make more sense to create a macro that closes and opens
the current document, as that is reported by the OP to fix the immediate
problem. e.g.

Dim sFname As String
With ActiveDocument
.Save
sFname = .FullName
.Close
End With
Documents.Open sFname


--
<>>< ><<> ><<> <>>< ><<> <>>< <>><<>
Graham Mayor - Word MVP

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



"Fumei2 via OfficeKB.com" <u53619(a)uwe> wrote in message
news:a72bcde41e065(a)uwe...
> As a suggestion, do NOT keep the Adobe add-ins loaded. I do not. I have
> a
> icon on the toolbar that:
>
> 1. loads the Adobe PDFMaker add-in
> 2. makes the PDF of the ActiveDocument
> 3. UNLOADS the PDFMaker add-in.
>
> The issue, as far as I can see, is that the .dot file of PDFMaker is
> generally kept loaded. It is in Startup. Bad idea. Frankly, I do not
> allow
> ANY add-in to be a permanent one.
>
> Jon Borel wrote:
>>A little more info: Although I can't run my macros until I close and then
>>reopen the document, Word's built-in macros seem to run fine (signs point
>>to
>>my macros). Also, a very simple "HelloWorld" macro continues to run after
>>PDF
>>(more signs point to my macros). I am running an application event
>>procedure
>>(SelectionChange)...
>>
>>> Hello,
>>>
>>[quoted text clipped - 16 lines]
>>> Thanks,
>>> Jon
>
> --
> Gerry
>
> Message posted via http://www.officekb.com
>


 | 
Pages: 1
Prev: PRINTDATE Field Calculation
Next: I want to catch the "Save on Exit" routine