MSO Access email needing verification - item.send

[Scott]

IS THERE A WAY TO TURN THIS VERIFICATION OFF????

I'm sending an auto email from Microsoft Access 2000.
When I do, I receive a pop-up box that states the
following:

A program is trying to send mail using Item.Send
A program is trying to automatically send e-mail using a
Microsoft Outlook Visual Basic Application command,
Item.Send. If you want this program to send this e-mail,
click Yes. To stop the program, click No. If you are
unsure which program is sending the e-mail or why, you may
want to click No to avoid any possible spread of viruses.

Note When this message is displayed, the Yes button is
not available for 5 seconds.

My barrier is that I need to send emails in between
procedures. This "verification" stops the rest of my
procedures from continuing until I click "yes". I can't
schedule tasks for down-time if I have to have someone
here to click the "yes" button to keep it going. Please,
if you know a way around this verification, let me know!!!

Thanks for the assistance, Scott

 

[Sue Mosher [MVP-Outlook]]

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. They
cannot be simply turned on or off with a user option or registry setting.

However, Outlook 2003 does not show security prompts on three specific types
of applications:

-- VBScript code in published, non-oneoff Outlook forms

-- Outlook VBA code that uses the intrinsic Application object

-- Outlook COM add-ins properly constructed to derive all objects from
the Application object passed by the OnConnection event

In earlier versions of Outlook, standalone users 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 and either your application needs
to support versions besides Outlook 2003 or your application runs extenal to
Outlook, you have these options for modifying your program to avoid the
security prompts (roughly in order of preference):

-- 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
recommends. However, it applies only to COM add-ins and external programs;
you cannot use Extended MAPI in Outlook forms or VBA.

-- Use Redemption (http://www.dimastr.com/redemption/), a third-party
COM library that wraps around Extended MAPI but parallels the Outlook Object
Model, providing many methods that the Outlook model does not support

-- 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
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers