I received confirmation from the owner of the Outlook object model that the
large Send button cannot be repurposed. He also confirmed the best
workaround would be to handle item.Send().

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


"GR" wrote in message
...

Hi Ken,

Thanks for looking at this. I'm glad it's not just me who sees this!

I have been playing with using the Item.Send() event in the meanwhile.
I think I might be able to get away with using this although it is
nowhere as efficient. I am having to write a lot more code than if I
could just capture that button's event when pressed. One particular
problem I have is that in Outlook 2007 by the time the Item.Send()
event is called, an occurrence of a recurring meeting that was opened,
modified and has had its "Send" button pressed now has had it's
RecurrenceState changed from "occurrence" to"exception" which was
messing up how I work with this item further downstream. It looks like
I can check this ahead of time though in the Item.Write() event which
comes first and it still is representative of the RecurrenceState of
the item when the user first opened it.

I really would like to be able to intercept that button though. Thanks
for all your help. Please keep me posted if you discover something.