Now-datz-a-what-I-call-a-service!

I was wondering if PRODID and VERSION WERE required properties?

The GUID (when I printed the VCS from my "my dummy" is certainly a long fellow!

I also noticed an ICS (awa the VCS). The ICS seems to have more info , but I dont fathom the difference. I assume the ICS has SMTP (just guessing) info embedded.

In the original thread - a document (vCalender, 1996) was noted. I have not reached the dicussion regarding SMTP vs MIME?

The app I am working on will reside on a server and I am [still] working out way to mail it. Any suggestions?:-)

Micheal - thank you so much for the response!

>>How did it turn out! Could you share some general info about your solution?
>>
>>>Is anyone out there familiar with the format of a vCalendar appointment? I need to send email notification to Outlook users from my app, and I would like them to be able to add it to their calendar by clicking or dragging.
>>>
>>>Most specifically, I need to know the significance of the UID in the message. Is it a GUID for the appointment itself? How can I safely generate one in my app?
>>>
>>>The rest of it looks pretty decipherable.
>>>
>>>TIA
>>>Michael
>
>Yes - I saved a vcs from a dummy outlook appointment and stripped out the stuff that seemed irrelevant. I then used string replacement to insert the proper data from my VFP tables. The content of the template became:
>

>BEGIN:VCALENDAR
>PRODID:-//Microsoft Corporation//Outlook 9.0 MIMEDIR//EN
>VERSION:1.0
>BEGIN:VEVENT
>DTSTART:<%= lcStDate   T<%= lcStTime   Z
>DTEND:<%= lcEndDate   T<%= lcEndTime   Z
>LOCATION;ENCODING=QUOTED-PRINTABLE:<%= m.EventLoc   
>DESCRIPTION;ENCODING=QUOTED-PRINTABLE:<%= m.Content   
>SUMMARY;ENCODING=QUOTED-PRINTABLE:<%= m.Subject   
>PRIORITY:3
>END:VEVENT
>END:VCALENDAR
>

>
>Since I stripped out the UID, Outlook will probably think appointments are conflicting if you click on the same appointment again. If I were to refactor, I'd probably generate a GUID for that from VFP.
>
>Another caution is that the date/time zone does not work across time zones (that is, it will always assume local time). That's because I had no way of telling what time zone each user was in (it's an internet application).
>
>A third caution is that in early and unpatched versions of Outlook, the time didn't import properly (Outlook was assuming the specified time was GMT or something). The patch was added years ago - about the same time as that stubborn confirmation message was added to warn users when an application wanted to do something in Outlook. If someone avoided that patch, then the imported appointment times will be wrong.
>
>HTH