Alan,
You're not doing anything wrong; what you are seeing is the built-in Outlook
Security Prompt, which appears when applications attempt to use certain
Outlook properties and methods. Had you set the last argument to True (Edit
the email before sending), Outlook itself opens and the security prompt does
not appear. The most complete list of possible work-arounds has been
provided by Outlook MVP Sue Mosher and is as follows:
BEGIN QUOTED MATERIAL:
"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,
