R
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?
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?