There is a problem that has been identified with calendaring...I'll list it
in a moment. The solution is listed on some other boards with a workaround,
but I haven't seen it here.
-------------------------
Environment A: PDA with Windows CE 2002, ActiveSync 4.x, Outlook 2003 on
WinXP Pro.
Environment B: Smartphone with Windows Mobile 5, ActiveSync 4.x, Outlook
2003 on WinXP Pro.
Condition: Outlook 2003 is configured to send out appointments using
iCalendar format. Problem manifests identically in both Environment A and B.
-------------------------
Situation 1: Create an appointment on mobile device, invite attendees, sync
device with PC and invitation sends normally.

Situation 2: On mobile device, modify the appointment from Situation 1,
sync device with PC and invitation sends normally.

Situation 3: On PC, modify the appointment from Situation 1 and invitation
fails to send update to attendees. It remains in outbox and Outlook reports
error ox800CCC13. Appointment syncs successfully.

Situation 4: On PC, for failed appointment, remove the "send as iCalendar"
setting under Tools, modify the appointment from Situation 1 and invitation
sends normally. Appointment syncs successfully.

Situation 5: Create an appointment on PC, invite attendees and invitation
sends normally. Appointment syncs successfully.

Situation 6: On mobile device, modify the appointment from Situation 5,
sync mobile device with PC and invitation sends normally.
-----------------------
I suppose it's a long-winded way of saying that an appointment created on a
mobile device and sync'ed with a PC loses something along the way. If you
try to modify that appointment later on a PC with the iCal format engaged, it
won't go anywhere. Where's the bug - mobile OS/iCal/Sync/Outlook?
Unchecking the iCal format setting makes the bug go away -- at least for
Outlook users. I would suspect that other calendaring systems depending on
iCal would have a problem with the workaround.

I've looked throughout the Microsoft site and cannot find this addressed --
neither the problem nor the workaround. Looks like a bug to me. Anyone else
experienced this? Has anyone heard of Microsoft addressing or attempting to
fix this problem?