ACCESS USING OUTLOOK

[Mike C]

I'm using access to send EMails to inform people of an
event that has happened within the database. Is there an
easy way to allow Access to send an EMail through Outlook
without getting the message telling you that a progam is
attemptint to send a message through Outlook?

 

[Sue Mosher [MVP-Outlook]]

No. See http://www.slipstick.com/outlook/esecup.htm#autosec for your
options.

 

[Mike C]

Are you trying to tell me to buy your book?

-----Original Message-----
No. See

http://www.slipstick.com/outlook/esecup.htm#autosec for
your

 

[Sue Mosher [MVP-Outlook]]

No, I'm trying to tell you where you can find information on how to work
around the security prompts. Did you look at the page I suggested?
--
Sue Mosher, Outlook MVP
Author of
Microsoft Outlook Programming - Jumpstart for
Administrators, Power Users, and Developers

 

[Mike C]

Yes I have, and I'm trying to wade through it. It's not
easy finding what you're looking for if you are
unfamiliar with all the catagories. I think I've found
the section that is applicable, but I'm not sure yet, as
I have to struggle with the computereeze. What I need to
see is "How to turn off warning pop up when Access is
attempting to send an EMail through Outlook." Then I
would know I'm looking in the right place. Then I need
the instructions to be in plain english, you know,
layman's terms. You know, click here, do this, type
in ....
I'll keep looking.

 

[Sue Mosher [MVP-Outlook]]

You won't find that because you can't turn it off if you're an end user. 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