Access and Outlook

  • Thread starter Thread starter Graeme
  • Start date Start date
G

Graeme

I have got a Database that is used to store Helpdesk
information and allocate jobs to members of the team using
Outlook Tasks. This uses the EmailSend function in an on
Click event and has been working fine until we recently
installed office 2000 service pack 3 onto our Citrix
Servers. When the button is clicked now we have to go
through 2 message boxes before the task is sent, these
message boxes are all generated from Outlook and say the
following:

Message box 1: ‘A Program is trying to access e-mail
addresses you have stored in Outlook. Do you want to allow
this?’ You then have to select a tick box to allow you to
have access.

Message box 2: ‘A Program is trying to automatically send
e-mail on your behalf. Do you want to allow this?’

Is there any way that I can get around this maybe using
code?

Thanks in advance.
 
The simplest and cheapest way to get around the Outlook Security Prompt is
to download and install the free utility, ClickYes, on each user's computer.

http://www.express-soft.com/mailmate/clickyes.html

Their website comes with sample code which you should incorporate into your
code to turn the utility on and off.

Other suggestions regarding the Outlook Security Prompt, as well as a wealth
of other information about Outlook can be found at:

http://www.slipstick.com/outlook/esecup.htm#autosec
 
Hi,
You can use Redemption. It is a com object that is used in conjunction
with the Outlook library.
Google on Outlook redemption

There is another method that automates the clicking of the message boxes.
I've never used it but you can find out about in at:
slipstick.com
 
If you'll post your code and tell me what concerns you have about
incorporating ClickYes, I'll be glad to see what I can do.
 
If you have access to your Exchange server, the following
gives information on Microsoft's workaround:

http://support.microsoft.com/default.aspx?scid=kb;EN-
US;263297

It's kind of a complicated solution, which incorporates
your Exchange server, a custom form to use for changing
security settings (be careful!), and registry key
settings that need to be deployed to anyone who uses the
application. But, it does work great once you have it set
up.

HTH
Joel
 
Back
Top