<div>
This is a security thing -- thank you so much Microsoft. &nbsp;A very simple solution is Express ClickYes. &nbsp;This little utility, when turned on, sits in the background and &quot;clicks&quot; the Yes button on any popup. &nbsp;I use it for this exact scenario.
</div>


<div>
Here you can find code samples to automate Microsoft Outlook directly with no irritating messages or prompts like a program is trying to automatically send e-mail on your behalf.<br />
<br />
With Outlook Security Manager you will need just a few lines of code to eliminate such alerts in Outlook 2000 - 2007. VBA, VB .NET, C#, C++, Visual Basic 6, Delphi, Word MailMerge, etc. are supported.<br />
<br />
<br />
You can find this example in the Demo Projects\SendMail subfolder of the &quot;Outlook Security Manager&quot; folder. It illustrates how to use Outlook Security Manager from any application that automates Outlook. With this sample project you can send e-mail messages using Microsoft Outlook as a &quot;mail engine&quot;. In this project there is a form, a simplified copy of the Outlook Mail window, with an Outlook Security checkbox.<br />
<br />
If you check this option, you disable Outlook Security and your application sends messages with no security warnings. Otherwise, you get a notorious security pop-up dialog box: A program is trying to perform an action that may result in an email message being sent on your behalf. (Or, is trying to send an e-mail message on your behalf). If this is unexpected, click Deny and verify your antivirus software is up-to-date. The prompt reads this way in Outlook 2007, or like in the screenshot below in earlier Outlook versions.<br />
<br />
<br />
<br />
To disable Outlook Security we use the DisableOOMWarnings property. But here is one peculiarity. To use Outlook Security Manager from inside of your Outlook &nbsp;Automation application you should connect it to the Outlook.Application object used in your application. So, you use the ConnectTo method of the TOlSecurityManager class. For example (you can find the following in the code below the form):<br />
<br />
Visual Basic .NET<br />
Dim SecurityManager As New AddinExpress.Outlook.Secur<wbr />ityManager<wbr /> <br />
SecurityManager.ConnectTo(<wbr />outlookApp<wbr />) <br />
SecurityManager.DisableOOM<wbr />Warnings = True <br />
Try <br />
&nbsp; '... any action with protected objects such as contacts or items... <br />
Finally <br />
&nbsp; ' In any case please remember &nbsp;<br />
&nbsp; ' to turn on Outlook Security &nbsp;<br />
&nbsp; ' after your code, since now &nbsp;<br />
&nbsp; ' it is very easy to switch it off! :-) &nbsp;<br />
&nbsp; SecurityManager.DisableOOM<wbr />Warnings = False <br />
End Try <br />
Visual Basic 6 (VBA)<br />
OlSecurityManager.ConnectT<wbr />o OutlookApp <br />
OlSecurityManager.DisableO<wbr />OMWarnings<wbr /> = True <br />
On Error Goto Finally <br />
&nbsp; '... any action with protected objects ... <br />
Finally: <br />
&nbsp; OlSecurityManager.DisableO<wbr />OMWarnings<wbr /> = False <br />
Delphi<br />
OlSecurityManager.ConnectT<wbr />o(outlookA<wbr />pp); <br />
OlSecurityManager.DisableO<wbr />OMWarnings<wbr /> := True; <br />
try <br />
&nbsp; //... any action with protected objects ... <br />
finally <br />
&nbsp; OlSecurityManager.DisableO<wbr />OMWarnings<wbr /> = False; <br />
end; <br />
Thus, if you want to disable Outlook security, use Outlook Security Manager and call the ConnectTo method before disabling Outlook Security.<br />
<br />
Please, make sure that you turned Outlook Security on inside the &quot;finally&quot; section, because Outlook Security Manager can potentially open a door for unsafe content. To avoid this you must enable Outlook security within a protected finalization code after each elementary call of the protected objects as we have showed in this example.
</div>


<div>
utlook Security Manager is developed and supported by MAPILab Ltd. together with Add-in Express Ltd. You can find the end-user version of Outlook Security Manager on mapilab.com.<br />
<br />

</div>


<div>
The other option here is to avoid outlook all together and send the e-mail directly to a SMTP server. &nbsp;There are several products that help with that; BLAT (command line utility or DLL callable via code), vbSendMail (which is a DLL + code), plugin from FMS, Inc. &nbsp;(<a href="http://www.fmsinc.com" rel="ugc">www.fmsinc.com</a>).<br />
There are others as well.<br />
Let me know if you want more detail on this approach.<br />
JimD.<br />

</div>


<div>
Like Jim D., I find that using CDO and SMTP to be the best and easiest method of mailing from Access. There's tons of code available for this method of mailing and you aren't constricted by Outlook.<br />
<br />
Regards,<br />
<br />
Jim
</div>


<div>
<div class="content wysiwyg-content">
When I send an object from Access to an email recipient, a warning pops up asking if I want to allow the email to be sent. &nbsp;This is a Microsoft Office Warning. &nbsp;How can I eliminate this warning.<br />
<a href="https://filedb.experts-exchange.com/incoming/2009/03_w10/112063/Email-Warning.gif" target="_blank" class="file-inline" title="Screen shot of the warning. (5 KB)"><svg xmlns="http://www.w3.org/2000/svg" viewBox="0 0 512 512"><path d="M67.508 468.467c-58.005-58.013-58.016-151.92 0-209.943l225.011-225.04c44.643-44.645 117.279-44.645 161.92 0 44.743 44.749 44.753 117.186 0 161.944l-189.465 189.49c-31.41 31.413-82.518 31.412-113.926.001-31.479-31.482-31.49-82.453 0-113.944L311.51 110.491c4.687-4.687 12.286-4.687 16.972 0l16.967 16.971c4.685 4.686 4.685 12.283 0 16.969L184.983 304.917c-12.724 12.724-12.73 33.328 0 46.058 12.696 12.697 33.356 12.699 46.054-.001l189.465-189.489c25.987-25.989 25.994-68.06.001-94.056-25.931-25.934-68.119-25.932-94.049 0l-225.01 225.039c-39.249 39.252-39.258 102.795-.001 142.057 39.285 39.29 102.885 39.287 142.162-.028A739446.174 739446.174 0 0 1 439.497 238.49c4.686-4.687 12.282-4.684 16.969.004l16.967 16.971c4.685 4.686 4.689 12.279.004 16.965a755654.128 755654.128 0 0 0-195.881 195.996c-58.034 58.092-152.004 58.093-210.048.041z"/></svg>Email-Warning.gif</a>
</div>
</div>


Email-Warning.gif

When I send an object from Access to an email recipient, a warning pops up asking if I want to allow the email to be sent.  This is a Microsoft Office Warning.  How can I eliminate this warning.

Email Warning

Interactions between email servers and clients are governed by email protocols. The three most common email protocols are POP, IMAP and MAPI. Most email software operates under one of these (and many products support more than one).  The correct protocol must be selected, and correctly configured, if you want your email account to work.

Email Protocols

Microsoft Access is a rapid application development (RAD) relational database tool. Access can be used for both desktop and web-based applications, and uses VBA (Visual Basic for Applications) as its coding language.

Microsoft Access

Microsoft applications include a variety of software programs, including development and digital authoring programs (Expression and Media Center), educational programs, Internet software, including Essentials, Skype and the Live family, anti-virus, productivity applications and suites like Office, Excel, Word, Outlook, Access and PowerPoint, video games and server applications such as Exchange, SharePoint, IIS and Virtual Server.