It's not a question of what is default behavior; it's having the ability to
attach events to dates, not just to time periods. Then you have the choice
and can choose appropriately for each event.
There are certainly events that are 24-hour periods with reference to a
particular time zone. "Christmas in Honolulu" can be thought of as one of
them. ("Christmas" is not. "Christmas in country x" where x has more than one
time zone is not.)

And a birthday or wedding anniversary is not. Outlook understands that when
birthdays and anniversaries are stored in contact records as dates, not time
periods. If it were otherwise, not only would it wrongly describe what these
events are, but you would need to know the time zone in which the contact was
born/was married/is in at this precise moment to correctly enter these
details, so is infeasible.

So Outlook gets this right in some places (Contacts) but wrong in others
(Calendar), behaving inconsistently. One result is a contact's birthday is
assumed to be a 24 event in the time zone you added the information in, which
is nothing to do with the the contact.

"Brian Tillman [MVP - Outlook]" wrote:

"DanZee" wrote in message
...

This is not just holidays or birthdays. The default behaviour doesn't make
much sense, the assumption that an "All Day Event" is a 24 hour meeting that
starts and ends at midnight in one particular time zone (and runs from 11PM
from 11PM one time zone away) is unintuitive.

Outlook 2007 helps with that. You can specify the intended time zone for the
event so that it will look OK in that time zone.

That said, I think it's VERY intuitive. Think of the REAL WORLD. It's
December 26 in Canberra when it's Christmas in Honolulu.
--
Brian Tillman [MVP-Outlook]
--
Brian Tillman [MVP-Outlook]