If you display an Outlook item modally the modality is only in relation to
Outlook. I don't think it necessarily would be modal to Excel or Excel code.

Displaying an Outlook item modally can also cause "ghost" Inspectors. When
the user closes the window an empty window remains until the user closes
that.

I don't know that using best practices with handling Outlook events is
necessarily overkill, but that's up to you.

--
Ken Slovak
[MVP - Outlook]
http://www.slovaktech.com
Author: Absolute Beginner's Guide to Microsoft Office Outlook 2003
Reminder Manager, Extended Reminders, Attachment Options
http://www.slovaktech.com/products.htm


"Michel S." wrote in message
...
Thanks again for your reply.

I realize that I used loop instead of
loop-waiting-only-for-a-window-to-be-closed, which is another way of
describing a modal window. ;o)

What are your thoughts about using " objMailItem.Display Modal:=True " in
an Excel class module and then simply return whether the MailItem Send
event fired or not ?


Just to recall the context: I only want to build OL mail items from
inside an Excel application, display each one to the user and record
whether or not he actually sent it as the mail window is closed..

Since I'm mostly an Excel and Access developer, I'm not very familiar with
Outlook gotchas, but having to implement and use the Item's Inspector
object only for that purpose seems a little overkill to me.

Am I missing something ? Any gotchas ?

Thanks