Here is a past post by MVP Cheryl Fischer on this subject which may help:
This is a built-in security message and unless you are running Exchange, you
can't disable it. Questions regarding the Outlook Security prompt are asked
very frequently, and the most complete answer has been provided by Outlook
MVP Sue Mosher as follows:
BEGIN QUOTED MATERIAL
"The security dialogs that pop up when an application tries to access
certain Outlook properties and methods are designed to inhibit the spread of
viruses via Outlook; see
http://www.slipstick.com/outlook/esecup.htm#autosec. If you are a standalone
user, Outlook provides no way to suppress this behavior. However, you can
use a free tool called Express ClickYes
(
http://www.express-soft.com/mailmate/clickyes.html) to click the security
dialog buttons automatically. Beware that this means if a virus tries to
send mail using Outlook or gain access to your address book, it will
succeed.
"If you're the administrator in an Exchange Server environment, you can
reduce the impact of the security prompts with administrative tools. See
http://www.slipstick.com/outlook/esecup/admin.htm
"If it's an application you wrote yourself, you can use one of these
approaches to redo the program:
-- Use Extended MAPI (see
http://www.slipstick.com/dev/mapi.htm) and C++
or Delphi; this is the most secure method and the only one that Microsoft
recommendeds.
-- Use Redemption (
http://www.dimastr.com/redemption/), a third-party
COM library that wraps around Extended MAPI but parallels the Outlook Object
Model
-- Use SendKeys to "click" the buttons on the security dialogs that your
application may trigger. See
http://www.slipstick.com/outlook/esecup.htm#autosec for a link to sample
code.
-- Program the free Express ClickYes
(
http://www.express-soft.com/mailmate/clickyes.html) tool to start suspended
and turn it on only when your program needs to have the buttons clicked
automatically."
--
Sue Mosher, Outlook MVP
Outlook and Exchange solutions at
http://www.slipstick.com
Author of
Microsoft Outlook Programming: Jumpstart
for Administrators, Power Users, and Developers
http://www.slipstick.com/books/jumpstart.htm
END OF QUOTED MATERIAL
[/QUOTE][/QUOTE][/QUOTE]
--
Jeff Conrad
Access Junkie
Bend, Oregon
Scott Duncan said:
Rick,
Thanks for the quick reply...
I will check into your suggestions. I am also looking to the Office 2003
Resource Kit to see if there is anything there
that can be used.
Thanks again !
SD
Rick Brandt said:
Scott Duncan said:
We use Access 2003 to automatically generate eMails for different events
such as shipment confirmations.
The statement is DoCmd.SendObject... and there is a Reference in the
Database to Outlook 11.0 Object Library.
Everything is working fine, except the last switch in the code is to Edit
[the eMail before sending] or not.
Since we want this as an unattended system, we have that switch set to no.
Outlook puts up a warning pop-up that there is a program that is trying to
automatically trying to send an eMail and that
if this unexpected... click NO.
Is there a work around ? Something in the registry that we can stop this
from happening ?
Nope. If you are using Exchange server there might be things that the
Exchange administrators can do, but the only thing you can do on the client
is NOT automate Outlook or MAPI (which is what SendObject uses).
I have been using the CDOSys library to send Emails whenever I don't need
to show them on-screen first. It does not trigger the security prompt.
There is a product called Redemption that is supposed to allow you to use
code similar to automating Outlook and not get the prompts. It did not work
when I tried it and even if it did you still would not be able to use
SendObject.
