Did you check your security state yet? If it says "administrator
controlled," that means that the Exchange administrator is controlling
security and, unless they loosen it for you, you won't be able to run VBA
code without security prompts.

--
Sue Mosher, Outlook MVP
Author of Microsoft Outlook 2007 Programming:
Jumpstart for Power Users and Administrators
http://www.outlookcode.com/article.aspx?id=54


"Sue Mosher [MVP]" wrote in message
...
Are you trying to create a rule for outgoing messages? The "run a script"
action is available only for incoming messages.

If you're getting security prompts with normal Outlook VBA code, using the
"run a script" rule isn't necessarily going to get around that. Maybe your
VBA code simply isn't constructed properly to derive all objects from the
intrinsic Application object. You might also want to tell us the security
state shown on the Help | About Microsoft Outlook dialog.

"laavista" wrote in message
...
I went through the steps you outlined multiple times, and there's no "run
a
script" rule. I wonder if my company "turned off" this option?

I was hoping to use this as the VBA procedure I wrote results in the
Outlook
Security Warning and is useless because of the warnings (my user would
have
to click 'yes' 400+ times a month). I thought by using the RunAScript
rule
it may prevent the warnings.

"Alan Moseley" wrote:

In Rules and Alerts click New Rule
Click 'Start From A Blank Rule' and choose a Step 1 option. Click Next
Select one or more conditions and click 'Next'
Under Select Action you should see an option for 'Run A Script', check
it
and click on the 'a script' hyperlink in the bottom window.
Choose the script that you wish to run.
Continue the remainder of the wizard.


"laavista" wrote:

I'm using Outlook 2003. I purchased an Outlook VBA book, and it
shows
examples of using the rules wizard "run a script". I do not see this
option
when I go into rules, and I would really like to use it.