> Is there any way at all to use the OutlookSecurity.oft form in Outlook
> without exchange server?
No.
> There has to be some way to work with Outlook
> other than a 3rd party extended mapi wrapper, coding around extended
> mapi ourselves, and an 'automagic click make dialog disapear'
> background process on the workstations.
There once was a way, and viruses took advantage of it to the extent that entire mail systems were brought to their knees. Perhaps you don't remember the spring of 1999.
> I'm sorry for knocking all the common solutions but they aren't
> acceptable just to make use of some 15 line macro's that cause the
> security dialog to appear. If there is any other way I would greatly
> appreciate some information about it.
Outlook VBA macros? Then your other solution is to upgrade to Outlook 2003, which "trusts" the Outlook object model for VBA use without triggering security prompts for objects derived from the intrinsic Application model in VBA.
--
Sue Mosher, Outlook MVP
Author of Configuring Microsoft Outlook 2003
http://www.turtleflock.com/olconfig/index.htm
and Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers
http://www.outlookcode.com/jumpstart.aspx