Sendobject Access 2002/Outlook

[Jan C.]

I recently upgraded Office (Access and Outlook) from 2000
to 2002. I can send an email message with an attached
report from Access with no problem. I have some macros
that run overnight that email reports using sendobject.
The emails sent from a macro with sendobject now cause
Outlook to pop up a window stating that a "A program is
trying to automatically send e-mail on your behalf. Do you
want to allow this?". This popup window halts further
processing in the macro. The popup window does not appear
when sending emails manually.
Why does Outlook allow on-line emails but not sendobject
generated emails? Is there a work around to this?
thanks in advance,
Jan

 

[Cheryl Fischer]

Questions regarding the Outlook Security prompt are asked very frequently.
The most complete answer has been provided by Outlook MVP Sue Mosher and is
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. [Note from Cheryl: One can and should use the code provided at
their website to programmatically turn ClickYes on and off. It works very
well.]

"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

hth,

 

[Jan C]

Thanks for the information. I could understand having this
problem if I was using a third party application or
something I had developed myself.
However, I am using Microsoft's Access product! The help
screen for the SendObject action from inside Access says:
"The SendObject action has the same affect as clicking
Send on the File menu, and the action arguments correspond
to the settings in the Send dialog boxes."
Well, the SendObject action does NOT have the same affect
as clicking Send on the File menu, because clicking Send
on the File menu does NOT bring up the security prompt
window. Using SendObject DOES.
Is anybody from Microsoft listening???? Why the difference?

-----Original Message-----
Questions regarding the Outlook Security prompt are asked very frequently.
The most complete answer has been provided by Outlook MVP Sue Mosher and is
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. [Note from Cheryl: One can and should use the code provided at
their website to programmatically turn ClickYes on and off. It works very
well.]

"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

 

[Guest]

Sorry, Jan. It IS frustrating. However, since Microsoft is the giant that it is and has the market share it does, it's also more prone to hacking and virus attacks. Many, if not most, of the new viruses these days are included in applications as macros. So, to let a user know that a PC is sending an email on his or her behalf is probably a good idea. If I recall, it is a function of the mail client software (Outlook, probably) and might be toggled off by a mail sysadmin.

The workaround I have is a msgbox telling the user that the next few boxes will tell him or her that the PC will be sending email on their behalf. This is NOT a virus and is a part of submitting their form to the engineering department. They should press OK and YES when so prompted

Hope this helps
Dere

----- Jan C wrote: ----

Thanks for the information. I could understand having this
problem if I was using a third party application or
something I had developed myself
However, I am using Microsoft's Access product! The help
screen for the SendObject action from inside Access says
"The SendObject action has the same affect as clicking
Send on the File menu, and the action arguments correspond
to the settings in the Send dialog boxes.
Well, the SendObject action does NOT have the same affect
as clicking Send on the File menu, because clicking Send
on the File menu does NOT bring up the security prompt
window. Using SendObject DOES
Is anybody from Microsoft listening???? Why the difference

-----Original Message----
Questions regarding the Outlook Security prompt are asked very frequently
The most complete answer has been provided by Outlook MVP Sue Mosher and i
as follows

BEGIN QUOTED MATERIAL
"The security dialogs that pop up when an application

tries to acces
certain Outlook properties and methods are designed to inhibit the spread o
viruses via Outlook; se
http://www.slipstick.com/outlook/esecup.htm#autosec. If you are a standalon
user, Outlook provides no way to suppress this behavior. However, you ca
use a free tool called Express ClickYe
(http://www.express-soft.com/mailmate/clickyes.html) to click the securit
dialog buttons automatically. Beware that this means if a virus tries t
send mail using Outlook or gain access to your address book, it wil
succeed. [Note from Cheryl: One can and should use the code provided a
their website to programmatically turn ClickYes on and off. It works ver
well.

"If you're the administrator in an Exchange Server

environment, you ca
reduce the impact of the security prompts with administrative tools. Se
http://www.slipstick.com/outlook/esecup/admin.ht

"If it's an application you wrote yourself, you can use

one of thes
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 Microsof
recommendeds

(http://www.dimastr.com/redemption/), a third-part

COM library that wraps around Extended MAPI but parallels the Outlook Objec
Mode

-- Use SendKeys to "click" the buttons on the

security dialogs that you
application may trigger. Se
http://www.slipstick.com/outlook/esecup.htm#autosec for a link to sampl
code

-- Program the free Express ClickYe

(http://www.express-soft.com/mailmate/clickyes.html) tool to start suspende
and turn it on only when your program needs to have the buttons clicke
automatically.

-

Sue Mosher, Outlook MV
Outlook and Exchange solutions at http://www.slipstick.co
Author o
Microsoft Outlook Programming: Jumpstar
for Administrators, Power Users, and Developer
http://www.slipstick.com/books/jumpstart.htm