What is your Mac OS version? 10.3.9 or 10.4.x? If 10.3.9 then you must
download and install the DST patch available earlier this year.
If 10.4.x then you must update to at least 10.4.5 (U.S.) or 10.4.6
(other DST changes) available about a year ago.
Keep in mind that old events that have the wrongtimemay need to be
manually updated.
Hope this helps!
--
bill
William M. Smith, Microsoft Interop MVP - Mac/Windows
Entourage Help Page <
http://entourage.mvps.org/>
Entourage Help Blog <
http://blog.entourage.mvps.org/>
Thanks for the info, Bill.
I'm running Tiger 10.4.10, and Entourage 11.3.8. This is happening for
new events (created today for the future), so I would assume that it's
not DST-related.
It appears that this problem occurs only when iCal creates an event
and invites an Entourage user. Here are my observations of such
events:
1. In the invitation email, the End Date is shown as January 1, 1601.
Clearly this is incorrect.
2. The event posts to the entourage calendar, BUT with a duration of
zero (even though the original event was created in iCal with a non-
zero duration, say, 1 hour).
3. The event does NOT initially show up in any of the Calendar views
(Month, for example). Apparently, this is due to the fact that the
duration is zero.
4. If you open the event in Entourage and manually change the duration
to a non-zero value, THEN the event will show up in Calendar views.
5. However, the event is still displayed with a start time one hour
earlier than the actual start time, as shown in the event itself.
Sigh. Alas, I'm forced to conclude that there is some incompatibility
between iCal and Entourage. For example, I know that iCal (in Tiger)
sends invitations with a START TIME and a DURATION (as opposed to an
END TIME). The RFC for ICS states that either and END TIME or a
DURATION can be used (but not both).
Incidentally, invitations sent by another instance of Entourage seem
to post correctly in all respects, so once again, it would appear that
there is some sort of disconnect between iCal and Entourage.
I've found posts describing this very problem in the Apple Discussion
Forum (
http://discussions.apple.com/thread.jspa?
messageID=5593388�) dating back to 2005, so you'd think this
problem would have been fixed by now!