<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN">
<HTML>
<HEAD>
<META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=us-ascii">
<META NAME="Generator" CONTENT="MS Exchange Server version 6.0.4630.0">
<TITLE>RE: [AccessD] Outlook's annoying habits</TITLE>
</HEAD>
<BODY>
<!-- Converted from text/rtf format -->
<P><SPAN LANG="en-au"><FONT SIZE=2 FACE="Arial">Hope and faith fading fast....</FONT></SPAN>
</P>
<P><SPAN LANG="en-au"><FONT SIZE=2 FACE="Arial">For Office XP the information you don’t want is in Q290500. "OL2002: Developer Information About E-Mail Security Features"</FONT></SPAN></P>
<P><SPAN LANG="en-au"><FONT SIZE=2 FACE="Arial">(</FONT></SPAN><A HREF="http://support.microsoft.com/default.aspx?scid=kb;en-us;290500"><SPAN LANG="en-au"><U><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">http://support.microsoft.com/default.aspx?scid=kb;en-us;290500</FONT></U></SPAN></A><SPAN LANG="en-au"><FONT SIZE=2 FACE="Arial">)</FONT></SPAN>
</P>
<P><SPAN LANG="en-au"><FONT SIZE=2 FACE="Arial">I note especially, the info near the bottom...</FONT></SPAN>
<BR><SPAN LANG="en-au"><B><FONT SIZE=4 FACE="Times New Roman">Avoiding the Security Features</FONT></B></SPAN>
<BR><SPAN LANG="en-au"><FONT FACE="Times New Roman">The e-mail security features affect all custom solutions that use the Outlook object model, CDO, or Simple MAPI, even if they are digitally signed. This includes the following:</FONT></SPAN></P>
<UL>
<UL>
<LI><SPAN LANG="en-au"><FONT FACE="Times New Roman">Outlook custom forms that are published to any folder or forms library, including the Organizational Forms Library </FONT></SPAN></LI>
<LI><SPAN LANG="en-au"><FONT FACE="Times New Roman">Outlook COM Add-ins </FONT></SPAN></LI>
<LI><SPAN LANG="en-au"><FONT FACE="Times New Roman">Outlook Visual Basic for Applications </FONT></SPAN></LI>
<LI><SPAN LANG="en-au"><FONT FACE="Times New Roman">Any other type of development project that uses the Outlook object model, CDO or Simple MAPI</FONT></SPAN></LI>
</UL></UL>
<P><SPAN LANG="en-au"><FONT FACE="Times New Roman">As a developer, you have various options when you try to avoid the security features. To summarize your typical options depending on where you are developing your solution: </FONT></SPAN></P>
<UL>
<UL>
<LI><SPAN LANG="en-au"><B><FONT FACE="Times New Roman">Outlook custom forms</FONT></B><FONT FACE="Times New Roman">: Publish forms so that they are not one-off forms, or use the administrator features to enable VBScript code in one-off forms to run. </FONT></SPAN></LI>
<LI><SPAN LANG="en-au"><B><FONT COLOR="#FF0000" FACE="Times New Roman">Outlook Visual Basic for Applications</FONT></B><FONT COLOR="#FF0000" FACE="Times New Roman">: Use the administrator features to disable object model restrictions, or convert your Visual Basic for Applications code to a COM Add-in, and then register it by using the administrator form. </FONT></SPAN></LI>
<LI><SPAN LANG="en-au"><B><FONT FACE="Times New Roman">COM add-ins</FONT></B><FONT FACE="Times New Roman">: COM add-ins can be trusted if an administrator registers them by using the administrator form. However, when you are using a COM add-in, only the Outlook object model is exempted; the CDO object model will still generate warnings.<BR>
<BR>
You cannot trust COM add-ins in Outlook 2000. This was a feature that was added to the Outlook 2002 version of the administrator form. </FONT></SPAN></LI>
<LI><SPAN LANG="en-au"><B><FONT FACE="Times New Roman">Automating the Outlook or CDO object models</FONT></B><FONT FACE="Times New Roman">: Use the administrator features to disable object model restrictions.</FONT></SPAN></LI>
</UL></UL>
<P><SPAN LANG="en-au"><FONT FACE="Times New Roman">If feasible, you may want to consider redesigning your solution so that it runs on a server instead of a client. Server-based APIs are not protected by these e-mail security features.<BR>
<BR>
You may also want to consider using a different messaging API or library: </FONT></SPAN>
</P>
<P><SPAN LANG="en-au"><FONT SIZE=2 FACE="Arial">….. Blah blah blah</FONT></SPAN>
</P>
<P><SPAN LANG="en-au"><FONT SIZE=2 FACE="Arial">Fine, but what are these administrator features, and where do I get one….</FONT></SPAN>
</P>
<P><SPAN LANG="en-au"><FONT SIZE=2 FACE="Arial">Bruce</FONT></SPAN>
</P>
<BR>
<BR>
<P><SPAN LANG="en-au"><FONT SIZE=2 FACE="Arial">-----Original Message-----</FONT></SPAN>
<BR><SPAN LANG="en-au"><FONT SIZE=2 FACE="Arial">From: accessd-bounces@databaseadvisors.com [</FONT></SPAN><A HREF="mailto:accessd-bounces@databaseadvisors.com"><SPAN LANG="en-au"><U><FONT COLOR="#0000FF" SIZE=2 FACE="Arial">mailto:accessd-bounces@databaseadvisors.com</FONT></U></SPAN></A><SPAN LANG="en-au"><FONT SIZE=2 FACE="Arial">] On Behalf Of Bob Gajewski</FONT></SPAN>
<BR><SPAN LANG="en-au"><FONT SIZE=2 FACE="Arial">Sent: Wednesday, April 30, 2003 2:58 AM</FONT></SPAN>
<BR><SPAN LANG="en-au"><FONT SIZE=2 FACE="Arial">To: 'accessd@databaseadvisors.com'</FONT></SPAN>
<BR><SPAN LANG="en-au"><FONT SIZE=2 FACE="Arial">Subject: RE: [AccessD] Outlook's annoying habits</FONT></SPAN>
</P>
<BR>
<P><SPAN LANG="en-au"><FONT SIZE=2 FACE="Arial">Also, Q291369 and Q291387 offer further insight ...</FONT></SPAN>
</P>
<P><SPAN LANG="en-au"><FONT SIZE=2 FACE="Arial"><snip></FONT></SPAN>
</P>
</BODY>
</HTML>