This software eliminates Outlook security pop-ups by using a single programming line. It can be used with several programming languages, including Visual Basic, C++, Delphi, and Word MailMerge.
Unlike similar tools, Outlook Security Manager does not change OOM and CDO calls to Extended MAPI calls. It also does not make development complicated with its own special objects. Instead, it implements one object with three properties that allow users to enable or disable Outlook Security Settings separately for OOM, CDO, and SMAPI.
Outlook Security Manager supports a range of programming languages like Visual Basic .NET, C#, C++ MFCL/ATL/.NET, Visual Basic 6, Delphi, VBA, Word MailMerge, and Excel MailMerge. It also supports all versions and service packs of Outlook including Outlook 2000, Outlook 2002 (XP), and Outlook 2003.
For example, Visual Basic .NET users can use the following code:
Dim SecurityManager As New AddinExpress.Outlook.SecurityManager
SecurityManager.DisableOOMWarnings = True
Try ... any action with protected objects such as contacts or items...
Finally SecurityManager.DisableOOMWarnings = False
End Try
Alternatively, in Visual Basic 6, VBA, and VBScript, the following code can be used:
OlSecurityManager.DisableOOMWarnings = True
On Error Goto Finally ... any action with protected objects ...
Finally: OlSecurityManager.DisableOOMWarnings = False
Delphi developers can utilize the following code:
OlSecurityManager.DisableOOMWarnings := True;try ... any action with protected objects ...
finally OlSecurityManager.DisableOOMWarnings = False;end;.
Overall, Outlook Security Manager is a great tool for those who want to manage and disable Outlook Security with ease. It is simple to use and supports a wide range of programming languages and Outlook versions.
Version 1.5:
ADDED:
Support of Borland Delphi 2006.
Support of Visual Studio 2005.
ALTERED:
Automatic initialization of the Simple MAPI sub-system when using the DisableSMAPIWarnings property in case it hasn't been initialized yet.
Version 1.3:
FIXED: Registration fails on Windows NT 4.0 SP3.
FIXED: The DisableOOMWarnings property doesn't work inside
Outlook.Application events trapped by a standalone application.
ADDED: Now Outlook Security Manager is thread-safe.
ADDED: Support of some new CDO versions.