From: Gary Britt 

OK, I understand your answer, I think.  You are assuming that everyone is
on Outlook (appropriate given the thread title) and somebody sends out an
appointment to each of the people who then click on it to cause it to be
scheduled into their local appointment book (or some similar scenario, do I
have this right).  In that kind of situation translation of time zones
would be necessary.

I don't ever have to deal with this which was part of my confusion, because
I don't use Outlook.  I use Sidekick 98 for calendaring and phone book.  So
I would never send out such a meeting note or use one.  I send an email or
or we do a telephone call.  We specifically agree on a time for a
particular time zone, and everybody then has to enter the day and time for
the meetings on their own in their own local time converting for time zone
differences.

Gary



Rich wrote:
>    This is not a shared calendar scenario.  This is a meeting with
> multiple participants in multiple time zones.  Quite common with
> teleconferencing.
>
>    As for the user interface for creating such a meeting, if you are the
> organizer you normally would set the time as the local time in your time
> zone.  This is automatically translated to local time for the
> recipients.  You can set it in another time zone if you wish if that
> makes more sense to you.  Again, it gets translated to local time for
> you and all recipients.  If any of the recipients moves between time
> zones, and changes the time zone of the computer, everything adjusts.
>
> Rich
>
>     "Gary Britt"      > wrote in message
>     news:45feaff6$1{at}w3.nls.net...
>     Except for a calendar shared across timezones.  It only makes sense to
>     schedule things based upon local time.  At least to me.  If I'm
>     going to be
>     on a conference call at X time.  I enter the local time for me.  The
>     parties
>     should translate timezones when setting up the meeting and each
>     participant
>     is responsible for putting down the right time for them on their
>     local calendar.
>
>     Someone mentioned shared calendars across timezones where there
>     could be a
>     problem, but for the life of me I can't imagine why somebody would
>     want to
>     share a calendar across timezones.  Everybody keep there own
>     calendar and is
>     responsible for their own calendar seems to make the most sense to
>     me.  Its
>     one thing to make the calendars viewable across timezones/offices
>     but to
>     make them actually shared seems a problem waiting to happen to me.
>
>     Gary
>
>     Rich wrote:
>     >    You would be wrong to schedule an 9:00 AM appt in CA as 9:00 AM
>     EST.
>     >  You schedule it for 9:00 AM PST or 12:00 PM EST, the actual time
>     of the
>     >  meeting.  I do the former because it is clearer for me.  Maybe it is
>     >  easier for you to think about a teleconference between you and
>     someone
>     >  in CA where what is at 9:00 AM for some participants is at 12:00
>     PM for
>     >  you and others.
>     >
>     >  Rich
>     >
>     >
>     >     "Gary Britt"      
>     >     >
wrote in message
>     >     news:45fe7d3b{at}w3.nls.net...
>     >     This doesn't make sense to me.  If I schedule a meeting in
>     >     California for
>     >     tomorrow at 9:00 AM, expecting to fly there from the East Coast
>     >     today, I
>     >     enter it on my calendar for 9:00 AM.  When I arrive in California
>     >     and pull
>     >     up my calendar I expect it to still say 9:00 AM.  Further, when I
>     >     schedule
>     >     it for 9:00 AM while on east coast local time, I don't expect to
>     >     enter it as
>     >     12:00 PM EST so it will show up on the calendar in California for
>     >     9:00 AM.
>     >
>     >     All appointments are scheduled for local time without regard to
>     >     timezones.
>     >
>     >     Gary
>     >
>     >     Geo. wrote:
>     >     >  "Gregg N"      
>     >     > wrote in message
>     >     >  news:45fd6769{at}w3.nls.net...
>     >     >
>     >     > > What is the reason for storing the time as UTC instead of
>     as local
>     >     > > time, given that local time is what is being scheduled?
>     >     >
>     >     >  Global corporations, I may travel to another office
and it would
>     >     need to
>     >     >  remind me at the correct time when I'm there.
>     >     >
>     >     >  Geo.

--- BBBS/NT v4.01 Flag-5