Apologies,this is a bit of a complicated mess. I have a macro in MS Access
that uses a macro written in Word as a part of an an import operation. The MS
Word macro "disappeared" last week. I was fortunatley able to recover the
macro, but it was disabled because it's certificates were no longer attached.
I signed the recovered macro, but now the MS Access database gives me an
error msg "Unable to Run Specified Macro" when I run its import operation
macro. When I hit the debug button, the command that calls the MS Word macro
is what is highlighted. The MS Word macro works fine when I run it alone; it
does exactly what it was programmed to do. However, ever since I signed the
recovered macro, MS Word takes at least 30 seconds to open. I am also
concerned that I'm not storing the recovered macro in the correct spot. I
haven't altered the MS Access macro, so I'm pretty sure the problem lies
somewhere with the MS Word macro. Any ideas on where to start the
troubleshooting process?
Chuck - 13 Jul 2005 16:56 GMT
Perhaps the reference to the macro was broken? Did you check in your Access
module whether the reference is active (Tools>References)?
Afraid I've got no ideas about why Word is taking so long to open...
Or is the macro
> Apologies,this is a bit of a complicated mess. I have a macro in MS Access
> that uses a macro written in Word as a part of an an import operation. The MS
[quoted text clipped - 10 lines]
> somewhere with the MS Word macro. Any ideas on where to start the
> troubleshooting process?
MissaHaarstad - 15 Jul 2005 09:05 GMT
It looks like the reference is good. I did mean the macro itself takes a
while to open.
> Perhaps the reference to the macro was broken? Did you check in your Access
> module whether the reference is active (Tools>References)?
[quoted text clipped - 17 lines]
> > somewhere with the MS Word macro. Any ideas on where to start the
> > troubleshooting process?