C
Chris C.
Hi,
I am creating a little MS Access "daemon" to check for e-mail notificatoins
it needs to send based on users' entered data. When it finds qualifying
rows, it's supposed to shoot off an e-mail via a docmd.sendobject, which is
working fine.
My problem is that at my institution we default to MS Outlook, and there's a
little security check in our install which prompts something to the tune of
"a program is trying to send an e-mail on your behalf. Do you want to do
this?", prompting for a Yes/No selection. Clearly, if I'm to automate these
e-mails, I am not going to watch for and answer these dialog boxes 24/7.
How can I avoid this? My institution isn't going to back off this rule.
Can I instruct VB to use another client, e.g., OE? How do I do this? Are
there other, even simpler e-mail methods that don't need to tap into a
workstation clients?
Chris
I am creating a little MS Access "daemon" to check for e-mail notificatoins
it needs to send based on users' entered data. When it finds qualifying
rows, it's supposed to shoot off an e-mail via a docmd.sendobject, which is
working fine.
My problem is that at my institution we default to MS Outlook, and there's a
little security check in our install which prompts something to the tune of
"a program is trying to send an e-mail on your behalf. Do you want to do
this?", prompting for a Yes/No selection. Clearly, if I'm to automate these
e-mails, I am not going to watch for and answer these dialog boxes 24/7.
How can I avoid this? My institution isn't going to back off this rule.
Can I instruct VB to use another client, e.g., OE? How do I do this? Are
there other, even simpler e-mail methods that don't need to tap into a
workstation clients?
Chris