From: "Rich" 

This is a multi-part message in MIME format.

------=_NextPart_000_02A2_01C769FA.347A01A0
Content-Type: text/plain;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

   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=20
  tomorrow at 9:00 AM, expecting to fly there from the East Coast today, =
I=20
  enter it on my calendar for 9:00 AM.  When I arrive in California and =
pull=20
  up my calendar I expect it to still say 9:00 AM.  Further, when I =
schedule=20
  it for 9:00 AM while on east coast local time, I don't expect to enter =
it as=20
  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=20
  > news:45fd6769{at}w3.nls.net...
  >=20
  >> What is the reason for storing the time as UTC instead of as local=20
  >> time, given that local time is what is being scheduled?
  >=20
  > Global corporations, I may travel to another office and it would =
need to=20
  > remind me at the correct time when I'm there.
  >=20
  > Geo.
------=_NextPart_000_02A2_01C769FA.347A01A0
Content-Type: text/html;
        charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable








   You would
be wrong to =
schedule an 9:00=20
AM appt in CA as 9:00 AM EST.  You schedule it for 9:00 AM PST or
= 12:00 PM=20
EST, the actual time of the meeting.  I do the former because it
is = clearer=20
for me.  Maybe it is easier for you to think about a
teleconference = between=20
you and someone in CA where what is at 9:00 AM for some participants is = at 12:00=20
PM for you and others.
 
Rich
 

  "Gary Britt" <GaryNOSPAMBritt{at}genera=">mailto:GaryNOSPAMBritt{at}generalcogster.com">GaryNOSPAMBritt{at}genera=
lcogster.com>=20
  wrote in message news:45fe7d3b{at}w3.nls.net...Th=
is=20
  doesn't make sense to me.  If I schedule a meeting in California =
for=20
  tomorrow at 9:00 AM, expecting to fly there from the East Coast =
today, I=20
  enter it on my calendar for 9:00 AM.  When I arrive in =
California and=20
  pull up my calendar I expect it to still say 9:00 AM.  =
Further, when=20
  I schedule it for 9:00 AM while on east coast local time, I don't =
expect=20
  to enter it as 12:00 PM EST so it will show up on the calendar in=20
  California for 9:00 AM.All appointments are scheduled for =
local time=20
  without regard to
timezones.GaryGeo.
wrote:> =
"Gregg N"=20
  <invalid{at}invalid.invalid>=20">mailto:invalid{at}invalid.invalid">invalid{at}invalid.invalid>=20
  wrote in message > news:45fd6769{at}w3.nls.net...>=
=20
  >> What is the reason for storing the time as UTC
instead of =
as=20
  local >> time, given that local time is what is being=20
  scheduled?> > Global corporations, I
may travel to =
another=20
  office and it would need to > remind me at the correct time =
when I'm=20
  there.> >
Geo.

------=_NextPart_000_02A2_01C769FA.347A01A0--

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