>Have you tried usin the appointment directly?
>
>

oApp = CREATEOBJECT('cdo.appointment')

Yes - with CDOEX. CreateRequest() is [also] firing and a message is sent. The received item, however looks an Outlook sent appointment (meeting) is sent to my mailer, Eudora (no calendar). The similarity is the fact that the CDOEX sent appoint when received by an outlook client has astra's and tildes (*~*~*~*~*~*~*~*~*~) in the message body just as the Eudora received [working] Outlook appointment! The CDOEX appointment, however, is not updating the calendar.

THe CDOEX sent appiointment arrives to an Outlook client as a plain text 8 bit message, while an Outlook sent appointment arrives as MIME (i think - or meeting object) and is placed in the calendar when opened.

The CDOEX samples make use of an exchange mailbox (iMBX) - an ADO object, The samples, it seems, Save() the meeting request to iMBX before Send()-ing. My test 'console' is not doing (Save()-ing) that before the Send()-ing. Maybe the missing pieces for the final rendering have something to do with iMBX????

I forget how a CDO message (w/o an appointmen) has it's content type set. It's just so close - it almost tastable.

The best route would be one that could crack the Outlook Meeting Request 'data stream'. The stream would be modified for recipients, dates, and attendees (etc), and then winsock chunked out port 25. (Some) port sniffers can do it, but not all decode outlook and then the issue of subtracting TP tags from the the capture still remains.

I've got bl;isters on my fingers from all the googleing and "tests".