Does the addin code run at all after that on that machine, or is the addin
getting disabled by an unhandled exception? If you open another item and
send it does the code fire? If not that would indicate an unhandled
exception as in my first question or something going out of scope. Other
than some rogue software on that machine that's all I can think of.

--
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
...

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.

Yes the addin still runs. I can open another email or several emails at one time and the addin still runs. It's quite strange so I was hoping someone had come across this issue before.

All I can say is if this is on just one machine that the only way to
ultimately figure it out will be to compare the differences on that machine
and try to eliminate them one by one until you narrow it down.

--
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
...

Yes the addin still runs. I can open another email or several emails at
one time and the addin still runs. It's quite strange so I was hoping
someone had come across this issue before.