Link to home
Start Free TrialLog in
Avatar of wrogge
wroggeFlag for United States of America

asked on

Security dialog when sending e-mails from Microsoft Access through Outlook

Thanks to a number of more intelligent users than myself, I have finished a project to e-mail individual report outputs to the expected recipients.

During the execution, however, I receive a security dialog (that waits) asking to 'Allow', 'Deny' or 'Cancel' on each and every e-mail message.

I have investigated this on numerous sites and they all direct to making a change in the 'Outlook', 'Trust Center' for the 'Programmatic Access' section.  I have modified this in both my Outlook 2007 (test platform) and my Outlook 2010 (production platform).  I have set them to the 'Never warn me about suspicious activity (not recommended)' setting.

This makes NO difference at all.  With a typical mailing being over 100 messages, the eventual user could sit there and keep clicking the 'Allow' option, but I would rather eliminate the dialog all together.

Please tell me there is a solution that actually works for this.
ASKER CERTIFIED SOLUTION
Avatar of Nick67
Nick67
Flag of Canada image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
I've been using vbMAPI from www.everythingaccess.com, and really like the product. It does not require any additional deployment items, as all the necessary code is contained in specailly created C packages directly in VBA. It completely avoids the security dialog, and also provides a wealth of other features.
...one more, in case money is no object
;-)

http://www.fmsinc.com/MicrosoftAccess/Emails.asp
Avatar of wrogge

ASKER

The mapilib did not work witht he dialog I was receiving yet the Click-Yes worked perfectly.  Just amazed that Microsoft's documented solution does not work.  Hurray for third party software.
<Just amazed that Microsoft's documented solution does not work>
MAPILabs is not Microsoft.  They are third-party too.
But, no matter what you may have read elsewhere, you cannot eliminate the Outlook Security Object Model with just settings.
We'd have all done that, including the virus-writers!, if we could.
I think what you probably read was about changing OUTLOOK's security settings.
Outlook itself can be locked down so that no code within Outlook works, or freed up so you can write VBA code in Outlook that will work

Glad ClickYes worked for you.