The security dialogs that pop up when an application tries to access certain Outlook properties and methods are designed to inhibit the spread of viruses via Outlook; see
http://www.slipstick.com/outlook/esecup.htm#autosec. They cannot be simply turned on or off with a user option or registry setting.
However, Outlook 2003 does not show security prompts on three specific types of applications:
-- VBScript code in published, non-oneoff Outlook forms
-- Outlook VBA code that uses the intrinsic Application object
-- Outlook COM add-ins properly constructed to derive all objects from the Application object passed by the OnConnection event
In earlier versions of Outlook, standalone users can use a free tool called Express ClickYes (
http://www.express-soft.com/mailmate/clickyes.html) to click the security dialog buttons automatically. Beware that this means if a virus tries to send mail using Outlook or gain access to your address book, it will succeed.
If you're the administrator in an Exchange Server environment, you can reduce the impact of the security prompts with administrative tools. See
http://www.slipstick.com/outlook/esecup/admin.htm
If it's an application you wrote yourself and either your application needs to support versions besides Outlook 2003 or your application runs extenal to Outlook, you have these options for modifying your program to avoid the security prompts (roughly in order of preference):
-- Use Extended MAPI (see
http://www.slipstick.com/dev/mapi.htm) and C++ or Delphi; this is the most secure method and the only one that Microsoft recommends. However, it applies only to COM add-ins and external programs; you cannot use Extended MAPI in Outlook forms or VBA.
-- Use Redemption (
http://www.dimastr.com/redemption/), a third-party COM library that wraps around Extended MAPI but parallels the Outlook Object Model, providing many methods that the Outlook model does not support
-- Use SendKeys to "click" the buttons on the security dialogs that your application may trigger. See
http://www.slipstick.com/outlook/esecup.htm#autosec for a link to sample code.
-- Program the free Express ClickYes (
http://www.express-soft.com/mailmate/clickyes.html) tool to start suspended and turn it on only when your program needs to have the buttons clicked automatically.
--
Sue Mosher, Outlook MVP
Outlook and Exchange solutions at
http://www.slipstick.com
Author of
Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx
"leonard hopkins" <(E-Mail Removed)> wrote in message news:068b01c38ac9$6f3b1b30$(E-Mail Removed)...
> Please tell me their is a way to disable this. We use the
> MS Project Workgroup addin when sendning project tasks.
> Now everytime a task is sent out from project, this damn
> message appears on every task item that is sent adding
> unwanted time. This is very annoying and I want to know
> how to stop it.
>
> New Programmability Behavior
> When you install the update, programmatic access to
> Outlook is restricted. If other applications try to use
> Outlook on your behalf, you receive a warning message and
> you are prompted to confirm what the other application is
> doing. You receive warning messages when another
> application tries to do anything in the following list:
> Send mail on your behalf
> Access your address book
> Access e-mail names from your messages
> Access e-mail information from your contacts or other
> types of items
> Save your messages to the file system
> Search your messages for content
> Use Simple Messaging Application Programming Interface,
> Simple MAPI, to send messages without your consent
>
Similar Threads
