Macros In Outlook 2003

[Guest]

Hi,

I have just returned from a job. The job was to install and run a VBA sript
that automated some outlook tasks.

When I clicked tools\macros\Visual Basic Editor nothing happened! In fact
nothing under 'macros' would do anything! Well when clicked the menu would go
away...

I tried everything that I could think of from removing the firewall,
re-installing outlook, and looking for references to VBA in the registry. No
joy anywhere, no error messages nothing.

Can someone give me a clue as to what might be happening?

VBA worked fine in Word and Excel, just not Outlook.

Regards,

Matt Sweeney.

 

[Guest]

Matt,

Macro security in Outlook typically defaults to "High". At this level, all
macros that are not digitally signed are disabled without warning. You
should check the macro security level and temporarily lower it to medium or
create a digital certificate using selfcert.exe which ships with Office.
Digital certificates created using selfcert.exe is only good on the machine
on which it was created and should be used for testing purposes only. If you
should decide to digitally signing your VBA project, you should then set the
macro security back to "High".

 

[Guest]

This sometimes happens after Outlook crashes. See if "VBA Editor" is listed
under Help | About Microsoft Office Outlook | Disabled Items.

 

[JaleDones]

Mark,

I have a similar problem (running a macro). My cohorts and I created a
macro to automate a task but due to the security settings it was
problematic. My action was to permanently set the security level to medium.
This is OK, I guess, but your message got me thinking.

Are you suggesting to "temporarily lower it to medium" via VBA code? If so,
how would I programatically code (code snippet please) a temporary lowering
of the security level, with the corresponding return to High Security at the
end of the macro?

Regards
Dale

 

[Guest]

Sorry, you cannot control the security settings through automation. Even if
you could, your code to set it to medium can't run if security is set to high!

If you want a guarantee that your code is run, develop it as a COM Add-In.