I wrote an application that I want to run on as a scheduled task on another computer in the office. It creates an HTML body Email and sends it via Outlook 2002. It runs fine on my machine but when I run it from the other MicroSoft Publisher keeps popping up like I'm trying to send a picture. I still get the Emails being sent to me from it. It sends around 100 Emails a run and I end up having to stop it and close all the publishing windows. I compared my Outlook settings to the other computer and I don't see any differences. Any suggestions?
This is NOT some spam mechinism I'm playing with here. We are a third party Doctor scheduling firm and these Emails are going to our Doctors with appointment notifications.
This just keeps getting weirder. In a subsequent test ADOBE reader kept popping up with the same document over and over. After I clicked it shut about a dozen times the program started running the way it should. That is a message pops up saying a program is trying to send an Email and do I want to allow it. Unless someone can point me in another direction I thinking it must be the ClickYes.exe I'm using so no human response is necessary to send the Email. I got it from here:
I have an app that runs continuously and sends out pager notifications when an unusual event occurs. I originally coded it to use Outlook. After some time, I began getting the popups. I then tried using MAPI, but had a similar result (the message was different - something about app accessing my address book). I wound up using the SMTP protocol to get around the popups.
I'm attaching the little test app that I wrote to work out the details. There are some comments at the end of lines where you will have to fill in your own information.
The popup is the Outlook Security Warning message. To get around it and still use Outlook you need to
write an Add-In and use the trusted application object that is passed in the parameters for the OnConnection event in
the designer module.
Otherwise use SMTP like previously suggested.
VB/Office Guru™ (AKA: Gangsta Yoda™ ®)
I dont answer coding questions via PM. Please post a thread in the appropriate forum.
Thanks for the responses. I ended up playing around with vbSendMail and it was pretty easy to set up. From what I've read and the couple of tests I did it should work fine for my purposes. The reveiws were pretty good. You can learn about it and get it from here:
So using this VBsendmail.dll, shall we read and send e-mails from outlook without getting the warning messages?
I guess I misunderstood your question. Outlook is not being used so it is not generating any warning messages. After the DLL is added the coding is just: