From: Gary Britt 

True Sidekick 98 is not the latest available software, but for me it has
better features and a better looking interface than Outlook 2000 (which I
also have), I've been using Sidekick since 1994 and before that I used
sidekick for dos from 1987 to 1993.  It does support some kind of group
scheduling, but I never used that either.  I think its group scheduling is
based upon everyone using Sidekick and having internet access.

If I'm mobile and traveling across time zones, just as I said earlier this
is what I do:  If I'm in Atlanta and schedule a meeting for the next day or
two weeks from today in San Francisco.  I schedule the meeting based on
local California Time (the actual time of the meeting in that actual
location using that locations actual time).  I write down in my calendar,
"meet with so and so at his office in San Francisco" next to the
appropriate line for the local time in California the meeting will take
place.  A 9:00 AM meeting is always 9:00 AM.  When I look at that
appointment I know it means 9:00 AM California time not 9:00 AM Eastern. 
When I'm in California and I'm at my hotel looking to see what time I need
to get a wake up call, I look at my calendar and it says I have a meeting
at 9:00 AM at so and so's office.  I know that means the same 9:00 AM as
everyone else in California is on.  Also, when I travel, I immediately
change my personal wrist watch to whatever local time is.  That way I can
use it and plan with it just like anyone else around me uses theirs.

I couldn't imagine doing either my Calendar or wrist watch any other way. 
I can understand that there might be some group situations where somehow
this isn't optimal, but I don't ever encounter them.  When I worked for a
company that liked to send out little outlook notices requesting an
appointment with me.  I would hit confirm or send a reply if there was a
conflict, but then I would enter the appointment in my Sidekick 98 calendar
as I never looked at or made any other entries to my outlook calendar.  It
didn't take long for other senior execs to catch on that "my"
outlook calendar didn't reflect my true calendar and only reflected by
accident appointments that somebody sent me an outlook request appointment
message thingy.


Gary


Rich wrote:
>    No.  I'm not assuming everyone is on Outlook.  If you look at the
> iCal standard for exchanging appts you will see that it mandates that
> some timedate info that is interchanged must be in UTC, others must have
> a delta from UTC, and some special case for appts in local time no
> matter where people are.  This strictness with time and time zones is
> for the same reasons I described.
>
>    I wouldn't be surprised if sidekick 98 had no concept of anything but
> local time.  Not very good for people that are mobile across timezones
> but it could be OK for simple use.
>
> Rich
>
>
>     "Gary Britt"      > wrote in message
>     news:45ff0d46$1{at}w3.nls.net...
>     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