orbitz
03-24-2006, 06:44 PM
Hi,
I was working a little project on ACCESS. One part of the application is to allow users within my department to submit their requests and upon the submission an automated email will be sent to my outlook and create task on my shared folder.
Everything works fine but I was wondering if we can prevent the warning message on the user's outlook being displayed. The message is like "an email is being sent out on his behalf" and the user has option to allow/not allow the email to be sent. I want to force the email to be sent. Can we do this?
Thanks!
slack
03-24-2006, 09:21 PM
You're better off just killing yourself.
I've never been less happy than writing VB code for Outlook and other Office applications. :)
Anyhow, I remember searching for this same problem years ago, and I'm pretty sure that there was no way around it other than to use different methods. Look into CDO.
This is one of those awesome ways that microsoft puts bandaids on security problems that just tick people off more than they help anything. Sometimes they're kind of humorous though I suppose...like outlook 2002 blocking .lnk attachments and IE sending pages via .lnk by default...so two extremely common MS internet applications suddenly don't work together to complete a very common task. Fantastic!
orbitz
03-24-2006, 09:31 PM
thanks. I will look into CDO to see what it offers :)
cprompt
03-25-2006, 08:41 AM
Outlook Redemption, http://www.dimastr.com/redemption/, will allow you to send emails via Outlook without those rediculous security messages screwing everything up.
orbitz
03-25-2006, 10:55 AM
Thank you. Well, the security message is not all rediculous. It is there to prevent malicious program such as virus to send out hundreds of email. About RDO, I doubt it that my company would allow me to use.
cprompt
03-25-2006, 01:42 PM
Actually, the security message is rediculous - it was a poorly designed, knee-jerk reaction from Microsoft and caused many applications to stop working correctly (mine included!) if Outlook was the default email client. While I do understand why they implemented it, it was a sledgehammer solution.
What they should've done is what they did with the XP firewall - if an application tries to send email, the user should get the message "application myapp.exe is trying to send email on your behalf, do you want to allow this?" and if yes, Outlook remembers that application and doesn't ask again. This is quite acceptable, in Microsoft's opinion, for a firewall, so why didn't they do the same for a lowly email client?
slack
03-25-2006, 03:40 PM
Thank you. Well, the security message is not all rediculous. It is there to prevent malicious program such as virus to send out hundreds of email. About RDO, I doubt it that my company would allow me to use.
Here's a page with some sample code using CDO to send a message:
http://www.sunny-beach.net/manual/591.htm
The benefit over MAPI is also that the user doesn't have to have an outlook express or outlook email profile on the machine for the program to work.
orbitz
03-25-2006, 04:07 PM
thanks Slack, I will try this.