outlook2003 converts recurring events into multi-day appointments

i have exactly the same problem as that described by gwen in her outlook2003 post. i am running server2003, as well as outlook2003. Timezones and dst settings are the same on all machines. but each time we set a recurring all-day event, within minutes outlook2003 changes it to a timed two-day recurring appointment running from 12 a.m. to 12 a.m., bracketed by a clock symbol at each end of the two-day "appointment." the timed "appointment" therefore ends on a different day from the actual event. this is very annoying, and essentially ruins the functionality of the shared calendar. and the same problem occurs on personal calendars viewed on different machines -- that is, a recurring event displayed properly on a desktop appears as a timed multi-day appointment when viewed on the laptop of the desktop's owner. i have written microsoft several times asking for a fix, but have not received (or found) one yet.

Alex, the DST check box was unchecked on the three
machines. Once I checked them it was fixed. Thanks to
Diane Poremsky for this solution!
-----Original Message-----
i have exactly the same problem as that described by
gwen in her outlook2003 post. i am running server2003, as
well as outlook2003. Timezones and dst settings are the
same on all machines. but each time we set a recurring
all-day event, within minutes outlook2003 changes it to a
timed two-day recurring appointment running from 12 a.m.
to 12 a.m., bracketed by a clock symbol at each end of
the two-day "appointment." the timed "appointment"
therefore ends on a different day from the actual event.
this is very annoying, and essentially ruins the
functionality of the shared calendar. and the same
problem occurs on personal calendars viewed on different
machines -- that is, a recurring event displayed properly
on a desktop appears as a timed multi-day appointment
when viewed on the laptop of the desktop's owner. i have
written microsoft several times asking for a fix, but
have not received (or found) one yet.

.

Thank you, Gwen! I checked again and found one errant machine, checked the DST box, and the problem seems fixed. Mea culpa!