Re: STILL IS NOT AVAILABLE... Run A Script not listed in rules wizard

Tech-Archive recommends: Fix windows errors by optimizing your registry

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


"laavista" <laavista@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:BD9B4898-5CA5-4993-B9C0-690935DEECF1@xxxxxxxxxxxxxxxx
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.


.

Relevant Pages

  • [NT] Heap Overflow in Windows Script Engine
    ... The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com ... Script Engine Could Allow Code Execution, ... * Microsoft Windows 98 Second Edition ... Outlook Express, remote attackers can exploit an integer overflow within ...
    (Securiteam)
  • Re: Form code events are not fired when editing an item based on the form
    ... When I create an item the script works. ... In the current Outlook security ... >> a button with an onclick event. ...
    (microsoft.public.outlook.program_forms)
  • Re: Forms Security
    ... That's what I though about the security issue, but why the PCs that were ... installed with Office XP execute the script and the PCs that had the Office ... > Sue Mosher, Outlook MVP ...
    (microsoft.public.office.developer.outlook.forms)
  • [NT] Flaw in Windows Script Engine Could Allow Code Execution
    ... The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com ... The Windows Script Engine provides Windows operating systems with the ... blocked by Outlook Express 6.0 and Outlook 2002 in their default ...
    (Securiteam)
  • Re: Forms Security
    ... Script won't run on unpublished forms, ... the Exchange administrator specifically allows it for all unpublished forms, ... if you're unfamiliar with this security provision. ... Sue Mosher, Outlook MVP ...
    (microsoft.public.office.developer.outlook.forms)