Outlook Security Prompts

[JordanChris]

Just in case you were interested:

Taken from Sue Mosher and therefore from www.Slipstick.com:


Microsoft has engineered a major change in Outlook 2003 that will
minimize the intrusion of Outlook security prompts for many users.
These prompts appear when programming code accesses certain features
that could let a malicious program harvest email addresses or send
messages. In earlier Outlook versions, a means to avoid those prompts
was available only to Exchange administrators willing to maintain a
special public folder and Outlook security settings form and to deploy
a new security registry entry to Outlook clients. Standalone users and
users in Exchange environments without the security settings form had
to endure prompts affecting everything from mail merge to customized
Outlook forms to some PDA synchronization programs.

In Outlook 2003, properly constructed Outlook COM add-ins, published
Outlook forms, and Outlook Visual Basic for Applications (VBA) code
don't trigger security prompts when the code uses certain Outlook
properties and methods. However, in Exchange environments in which the
administrator has deployed the security settings form and registry
entry, the security form settings still control the security prompt
behavior. Users and administrators alike should be delighted with this
"best of both worlds" approach, in which the administrator can still
control the security behavior but standalone users regain control over
their own VBA code and the many available Outlook COM add-ins.

Users, however, continue to get Outlook security prompts in VBA code
in Microsoft Word, Excel, and other Office 2003 programs and in any
programs external to Outlook that use Outlook programming objects. Why
does Outlook VBA suppress prompts although other environments don't?
In Outlook 2003, Microsoft implements Outlook VBA as a COM add-in.
Therefore, like other Outlook COM add-ins, Outlook VBA doesn't
generate security prompts. Note, though, that the security prompt
suppression affects only Outlook objects. Developers who use
Collaboration Data Objects (CDO) 1.21 in Outlook VBA or a COM add-in
still see prompts when they use address-related or message-sending
features in their code.

[TheBionicOrange]

Good ... because thats a pain in the ass !!