Macro won't automatically run after a restart

[Ray T.]

I have built a macro for Microsoft Outlook 2003. I have associated it with
my self-certified certificate. I have distributed both the VbaProject.OTM
file and the certificate to hundreds of machines. I have had them import the
certificate and add/replace their own VbaProject.OTM files. I have had them
trust the publisher of the certificate and enable macros after the software
was placed on their machine... The macro works perfectly for as long as they
have Outlook open. However, if they close Outlook and/or restart their
machine, the macro fails to run automatically. The user must select
Tools-->Macro-->Visual Basic Editor just to get Outlook to begin running the
macro again. They are not asked to trust the publisher of the certificate
again, nor are they asked to enable macros again. However, unless they
follow this seemingly useless step of bringing up the Visual Basic Editor,
the macro will not run after a reboot/restart. I would like to avoid this
situation and have the macro always running once they've trusted/enabled it
once. Their security settings are set at "High" but that should be fine even
with a self-certified certificate... I don't understand what's happening...
Has anyone else seen this behavior and are there any tricks to avoid it?

 

[Eric Legault [MVP - Outlook]]

What happens if you reduce the Macro Settings settings to Medium or Low?

Ideally, you should port your macros to an Outlook COM Add-In - it'll make
distribution far easier.

--
Eric Legault - MVP - Outlook
MCDBA, MCTS (Messaging & Collaboration, SharePoint Infrastructure, WSS 3
Application Development, MOSS 2007 Application Development)
Blog: http://blogs.officezealot.com/legault
Try Picture Attachments Wizard for Outlook!
http://www.collaborativeinnovations.ca

 

[Ray T.]

Eric,

I had tried reducing the Macro Security settings to Medium (but not Low) and
that did not help... I will research your suggestion of "porting" the macros
to an "Outlook COM Add-in"... I don't know what that means at the moment, but
I'll see what I can find out!

Thanks,
Ray

 

[Eric Legault [MVP - Outlook]]

Sorry - "porting" is an uber-geek term for translating/converting. Most of
the code will stay the same, but "producing" the solution is quite different
and requires Visual Studio.

This page can get you started:

Developing COM Add-ins for Microsoft Outlook:
http://www.outlookcode.com/article.aspx?id=36

Eric