Try setting MeetingStatus. The order in which things are set can also be
important. Usually you set MeetingStatus first and then Location, Subject,
Start, Duration (or End), then recipients. Also add each Recipient object
separately and set the Recipient.Type to whatever you want (required =
olRequired).
See the help in the Outlook VBA in the Object Browser for MeetingStatus to
see a VBA code example.

Signature
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
> Hi,
>
[quoted text clipped - 28 lines]
> End If
> End With
Andy - 28 Jan 2008 13:11 GMT
Excellent - Thanks Ken.
One subsidiary question - that promt that a program is trying to send an
item (which you have to click Yes to once the Yes button appears). I
recognise the need for this to protect use from malicious macros but if we
have written the code ourselves and it is running on our own machine - can't
that warning message be suppressed?
Thanks again.
> Try setting MeetingStatus. The order in which things are set can also be
> important. Usually you set MeetingStatus first and then Location, Subject,
[quoted text clipped - 37 lines]
> > End If
> > End With
Ken Slovak - [MVP - Outlook] - 28 Jan 2008 15:53 GMT
In Outlook 2003 and later if you write VBA code in the Outlook VBA project
and derive all of your Outlook objects from the intrinsic Application object
the code is trusted usually.
External code on Outlook 2007 is trusted if the machine has an up-to-date
A-V and has the settings set to allow external trusted code.
Otherwise you have to use one of the workarounds listed at
http://www.outlookcode.com/article.aspx?id=52.

Signature
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
> Excellent - Thanks Ken.
>
[quoted text clipped - 6 lines]
>
> Thanks again.