>>Sergey,
>>
>>Well I read the spec and tried some real simple examples. This isn;t working for me in Outlook. The example I tried was a VTODO item and Outllok raised the error "Cannot import vCalendar file." without providing any hints. I stripped out all non-essential elements but it did not seem to matter. Then I found this statement, "And Outlook does not support the VTODO and VJOURNAL types of iCalendar items, only VEVENT." at this site:
>>
>>
http://www.slipstick.com/outlook/share.htm>>
>>So I tried editing my VCS file to change the VTODO item to a VEVENT item, but I still got the same error. FWIW, here is an example of something that did not work:
>>
>>BEGIN:VCALENDAR
>>VERSION:1.0
>>BEGIN:VEVENT
>>DCREATED:20020310T113000
>>LAST-MODIFIED:20020310T113000
>>STATUS:TENTATIVE
>>DUE:20020313T193000
>>SUMMARY:Dinner at 8
>>DESCRIPTION;ENCODING=QUOTED-PRINTABLE:Dinner today!
>>END:VEVENT
>>END:VCALENDAR
>>
>>I also tried exporting a task from Outlook 2000 to see what it might look like, but there was no option to create a vCalendar file, only message files (MSG), which looks to be a binary, possibly proprietary, format.
>>
>>Any ideas?
>>
>>-- Randy
>
>Maybe this will help
>
>OL98: How to Use vCalendar in Outlook 98 mskb #
Q179431>OL2000: How to Use vCalendar in Outlook 2000 mskb #
Q197025>OL2002: How to Use vCalendar in Outlook 2002 mskb #
Q287625Thanks. I have it working now for VEVENT's. The problem was that in trying to get it working for VTASK's (which is what I would really like but it doesn't support), I stripped away fields thinking that was the problem. When I then tried it as a VEVENT, I had removed a field that Outlook considers "required" -- DTSTART. Of course it gave me no clue of what it didn't like. Putting that back into a VEVENT seems to work just fine now.
-- Randy
