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.

Signature
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
> Hi
>
[quoted text clipped - 8 lines]
>
> Regards
Jenny Tam - 12 Sep 2003 20:27 GMT
Thank you, Sue, for your detailed response! It really helps me!
I found this security update very very annoying as well, so I'm
seriously thinking of rewriting my Outlook COM addin using Extended
MAPI in VC++ instead. But I do have questions:
(1) Does using Extended MAPI guarantee that I will NOT see these
security warnings regardless of what I do in Outlook 2000, Outlook XP
and Outlook 2003?
(2) Any good books/tutorials/samples on Extended MAPI for beginners?
Most samples I found either applies to Outlook prior to Outlook 2000
... or using VC++ 5.0 or earlier ... I'm using Visual Studio .NET
2003.
Just a note though, I still prefer doing it using ATL/COM/C++.
Any response is appreciated!
Jenny
> The security dialogs that pop up when an application tries to access
> certain Outlook properties and methods are designed to inhibit the
[quoted text clipped - 62 lines]
> >
> > Regards
Sue Mosher [MVP] - 12 Sep 2003 20:53 GMT
1) AFAIK, yes. That's the interface that Microsoft itself uses, as do all the PDA sync tool providers, etc.
2) No, because it's definitely not for beginners. Extended MAPI requires C++ or Delphi, although a few people are trying to find a way to make it work with .NET. See http://www.slipstick.com/dev/mapi.htm for resources

Signature
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
> I found this security update very very annoying as well, so I'm
> seriously thinking of rewriting my Outlook COM addin using Extended
[quoted text clipped - 8 lines]
> ... or using VC++ 5.0 or earlier ... I'm using Visual Studio .NET
> 2003.