In any open form you have 2 intrinsic objects you never have to declare or
instantiate: Item (the form) and Application (the Outlook.Application
object). So you don't use CreateObject to get a handle to
Outlook.Application, you use the intrinsic Application object of the form.

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


"djohnson" wrote in message
ups.com...

Sue wrote:
Instead of using To, you should call Item.Recipients.ResolveAll on the
original item, and if that returns True, iterate the Item.Recipients
collection and create matchin recipients on the new outgoing item.


I did that; thanks for the advice.


Never use CreateObject to create a new Outlook.Application object in your
custom form code. Use the intrinsic Application object that is already
available to you.

Would the intrinsic Application object be the Form Item? Maybe I
misunderstand. It was my understanding that this would send the whole
form including the code and end up creating a pane warning on the
recipients' end, which I was trying to avoid (not sure who would want
that). Since I only need code on the sender's end I don't want to send
the whole form.