View Single Post
  #3  
Old September 15th 09, 02:33 PM
amh amh is offline
Junior Member
 
First recorded activity at Outlookbanter: Jul 2009
Posts: 8
Default

Ken,

If it was code I should have the same problem across all the machines. Again it's just specific to one XP/Outlook 2003 machine. If I create a new email, enter "abc" in the to: field then click send, the outlook send event runs first before our custom code and notifies me I have an invalid recipient, I fix it and then click send again and my custom code never fires. So it seems whether it's Outlook canceling the send or our custom code canceling the send, the next time the send button is clicked our code is never called again. Let me know if you have any additional insight. Just to reiterate it's specific to a machine. I have 5 machines running xp/Outlook 2003 and 5 running vista/Outlook 2007 and the issue only occurs on one of the xp machines.


Quote:
Originally Posted by Ken Slovak - [MVP - Outlook] View Post
It sounds to me like you're releasing something after that first Send()
event so your event handler is going out of scope or being garbage
collected. Check for that in your code.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Professional Programming Outlook 2007.
Reminder Manager, Extended Reminders, Attachment Options.
http://www.slovaktech.com/products.htm


"amh" wrote in message
...

I have a custom addin that runs code when the mailitem.send event is
fired, however in certain cases the mailitem.send is not fired and it
skips to the application.itemsend event and i don't know why.

Here's the scenario. Compose a new email click "send", mailitem.send
event is fired but due to custom code it appropriately cancels the
event. I then click "send" again, the mailitem.send event is skipped
and the application.itemsend event fires. I don't want to have any
custom code behind the application.item send. I can run the same
scenario on different machines and only find the problem with one
configuration but I can't figure out what it could be. This problems
occurs on specific Windows XP/Outlook 2003 machines.

Any help would be apprecatied.




--
amh
Ads