Automate SendObject in macro

  • Thread starter Thread starter Bob
  • Start date Start date
B

Bob

I am trying to get SendObject to run in a nightly job
without answering the message box that is generated out of
the SendObject function. I have tried using the SendKeys
function but I haven't been able to make that work for
this either.
 
When I issue the SendObject command, I always get a box
with the following statement/question - "A program is
trying to automatically send e-mail on your behalf. Do
you want to allow this? If this is unexpected, it may be
a virus and you should choose "No"." There are 3 button,
Yes, No and Help. All of the documentation states that
there is a 5 second delay before the Yes button is
activated and I have been unsuccessful getting SendKey to
work.
 
Ah, ok. This has nothing to do with SendObject, and in fact nothing to
do with Access. This is related to the security feature of your email
software, presumably Outlook. I don't know of any way to handle this
directly. You might have a look at
http://www.express-soft.com/mailmate/clickyes.html
Another third party tool, which I personally use, that gets around the
limitations of SendObject, but you would have to justify the cost, is
Total Eccess Emailer, available from www.fmsinc.com.
 
Bob-

This is a common question in the
microsoft.public.outlook.program_vba newsgroup. One of the
gurus there is Sue Mosher. I am going to quote her
response to a similar question:


<<
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.
 
Back
Top