Timezone support

Hello,
I am from germany and visiting the states. As I arrived into the states my phone changed timezone as normal. But in the calender app all dates are changed times (-6hours), too and are incorrect now. I switched on the timezone support and all dates are shown correct now. But if timezone support is activated the appointments are correct but the current date is wrong. My calender app shows me the date of tomorrow what is correct if I would be in germany. But I am in Atlanta!
What do I have to do to make the app work properly?
Thanks in advance
Nophret

16-Oct-2008 12:15 PM
topend wrote:
The question is, does anyone from Nokia actually pay attention to these forums?
what's the use of having them if they're not paying attention and resolving what seems to be a very straight forward issue.
The answer to the first question is "no", apart from forum moderators.
These forums are for user-to-user interaction.
If you want to get hold of Nokia themselves then use the "Contact us" link to the top-right of this page.
Message Edited by grschinon on 16-Oct-2008 12:27 PM
Was this post helpful? If so, please click on the white "Kudos!" star below. Thank you!

Similar Messages

  • Provide Timezone Support

    Hi,
    We have an application which we are wanting to introduce timezone support. The DB server resides and runs in GMT but now have clients who could be based anywhere in the world.
    Has anybody any experience in converting a system from the old DATE to using the TIMESTAMP WITH LOCAL TIME ZONE?
    Also have many forms, reports, Pro*C modules which would need looking at. What would be involved in this task?
    We are running 9.2 with 9iAS and forms/reports 6.
    Any help appreciated.
    Many Thanks

    get the info of the client time zone and compare it with the installed one.
    you can store all this info in a oracle table and can perform your desired action.

  • ICal Timezone support - Birthday off by one day.

    I always used iCal's timezone support. I had it on since day one I got my computer running. I have been using the birthday calendar function for all my address book contacts' birthdays as well.
    I have just moved from Vancouver (GMT -7) to Japan (GMT +9), and now all my contact's birthday is off by one day. I tried turning off the iCal timezone support but not much happened.
    What can I do?

    I've had this same issue 2 times now (I'm also on the same setup as you).
    What has worked for me is the workaround listed here:
    http://www.macosxhints.com/article.php?story=20070313180838582
    To simplify, copy the script shown in the last post into a text file called:
    correctBirthdays (no file extension such as .txt is necessary)
    and save it into your home directory. Once you've done that:
    1. Back up your Address Book with the 'File > Back up Address Book...' menu item
    2. Open the Terminal application
    3. In Terminal, type *chmod 755 correctBirthdays* to make the script executable.
    4. Type *./correctBirthdays -1* and hit enter. If you're coming back from Japan, you'll want to use 1 instead of -1 to move the birthdays forward instead of back a day.
    5. That's it. Terminal will report how many birthdays were corrected.
    I'm guessing that this problem has been fixed in Mac OS X 10.5 Leopard, and that's why musicale can't reproduce the issue.
    Hope this helps!
    (and I take no responsibility if you mess something up! It should work though.)
    Rafael

  • Oracle timezone support

    Hello All,
    We are using Oracle 10 g. the database follows European timezone and we operate from USA. I am working on timezone dependent code and facing issues with it, any guidance will be a great help.
    When I use the query:
    1. "select current_timestamp from dual" I get time displayed in US timezone.
    2. "select systimestamp from dual", I get time in European timezone.
    No issues with the results of any of the above query, but when I use
    A* select extract (*hour from current_timestamp*) from dual; I get Hour displayed as ( European time - 1 ).
    B* It always gives Hour for a weird timezone, even if I change the timezone for the session by using "alter session set time_zone = 'EST' "
    Can someone please throw some light on this ?

    get the info of the client time zone and compare it with the installed one.
    you can store all this info in a oracle table and can perform your desired action.

  • How to Hide Timezone in Month View in Calendar App?

    I live in two timezones and go back and forth often so I use the timezone support in Calendar app for Mavericks and on my iOS devices and it's quite useful. However, one thing about it really stinks, imho.
    I cannot find a way to hide the timezone information associated with individual events in the month view of the Calendar desktop application. This redundant and superfluous information results in the truncation of the event information, which *is* important to me.
    For example, instead of an event in month view being displayed as "check amex payment", as it was before I enabled timezone support, it now says "check a... 3AM GMT+7". Since every event has this appended timezone information displayed next to it the month view of my calendar has become much less useful than it was previously. I don't really need to know how many hours ahead of GMT an event is, I pretty much just want to know what the event is and on what day, in the month view. Now I cannot tell what any event is unless I open it in in week or day view. Very frustrating.
    If anyone knows of a way to hide that information in the month view it would be greatly appreciated to post it here.
    thanks Apple Community!

    No one else has this problem or knows of a solution? *weeps quietly*

  • ICal Timezone Selection and Naming

    A few OS revisions past timezones were named with some at times distant association to UTC standards and could be attached to an event. Type in Eastern Standard or just Eastern and up came timezones with that in their name. Simple right, if you knew the name of the timezone you were planning the event for? Seems reasonable, if you are scheduling events for different time zones you might, nay probably, knew the name of the timezone. Or could easily find it online.
    As I recall you could also type the name of a city like Cleveland or Stockton, or even some more obscure places like Vienna or Paris, and get the same results.
    Apple changed it, to remove any confusing references to actual standard timezone names when selecting, ahem, a timezone. Nor can you select by offset from UTC (0) known to most as GMT, which was also an available choice.
    One currently has to name a city or large town that Apple has deemed worthy of inclusion, and while shock of shocks the US database of cities, towns and hamlets is fairly well populated, those outside the US  appear to have been selected by a bored intern who snuck a bottle of beer in armed with a dart and a word map.
    Requiring one examine, from an example I prepared earlier, the map of Western Australia searching for a town that appears significant enough to perhaps have been included in said timezone popup menu by Apple that is also located near Grass Patch (look it up), and hopefully happens to be in the same timezone is an exercise in almost random guesswork. Take a look at a timezone map of Australia if you think they are all stacked neatly side-by-side with borders as straight and dull as a Texas town main street.
    I own a computer to avoid error inducing, repetitive, dull activities that could better be done by a well trained pidgeon. It is, obviously I suppose, very irritating and ironic that it was a desire to avoid such errors that was the reason one turned on timezone support in the first place.
    You also have to know in advance, or try possibilities at random, the name town or city hoping that it appears in the Apple town-or-city-name-apparently-chosen-at-f*****g-random-and-associated-with-a-tim ezone popup menu in your effort to select the same timezone as your event attendee. Proximity does not guarantee a town is the same timezone after all. Often a distant town or city in the Apple popup will be in the same timezone, while one nearby is not. But you cannot know for certain without trawling through the internet and wikpedia to work this out because most maps do not include delineations of the various timezones.
    In this case Apple has made a mistake in deciding what not to do. Removing a perfectly usable, well not perfectly but better than this, existing system in place as an option was an error.
    By removing standard UTC codes, or something approximating them (you know the international standard naming convention for timezones that has been abandoned in an application trumpeting its adoption of standards), instead of just leaving them available alongside the calendrical equivalent of Soma, may, may, have made the system easier for people unfamiliar with timezones. But I doubt it, it is more likely to guarantee continued ignorance based on increased confusion engendered by use of a system providing no pattern or framework for understanding the concept of timezones, and it is a pain in the rear for anyone else.
    It also is part of a trend previously only inflicted on Windows users routinely of attempting to make things simpler for more people while making it impossible or more difficult to someone who knows what they are doing. I have no objection to providing simpler alternatives, just stop taking away more elegant if intellectually "demanding" ones already in existence.
    Looking up what city is nearby in the hope it is on the magic list for every one horse town a client might live in instead of just being able to type one of the Australian UTC standard timezones as provided by the client, or pick an offset of +8 hours in the above example is patronising, absurd, time consuming, and prone to errors.
    Is there anyway I can use the terminal to edit the pop up list of time zones or substitute a different one referenced by iCal? Or to restore something resembling a standard pop up list ordered by offset from UTC 0, otherwise known as GMT? If I could simply pick an offset of -8, or +5 hours, as examples, life would be a lot happier in iCal. Because even if I have to determine some offsets, as in the WA example above, doing so is as simple as typing "What is the time in <insert name of obscure s******e here> <name of country here> in my browser bar and hitting Enter.
    Yes I know that means I may have to do addition or subtraction, but I have the Apple Calculator for anything over 2, and somehow it has been spared any attempts to simplify its use.

    I've had this same issue 2 times now (I'm also on the same setup as you).
    What has worked for me is the workaround listed here:
    http://www.macosxhints.com/article.php?story=20070313180838582
    To simplify, copy the script shown in the last post into a text file called:
    correctBirthdays (no file extension such as .txt is necessary)
    and save it into your home directory. Once you've done that:
    1. Back up your Address Book with the 'File > Back up Address Book...' menu item
    2. Open the Terminal application
    3. In Terminal, type *chmod 755 correctBirthdays* to make the script executable.
    4. Type *./correctBirthdays -1* and hit enter. If you're coming back from Japan, you'll want to use 1 instead of -1 to move the birthdays forward instead of back a day.
    5. That's it. Terminal will report how many birthdays were corrected.
    I'm guessing that this problem has been fixed in Mac OS X 10.5 Leopard, and that's why musicale can't reproduce the issue.
    Hope this helps!
    (and I take no responsibility if you mess something up! It should work though.)
    Rafael

  • Showing Timezone in calendar

    I am frequently moving between timezones and get meeting invites from other parties for events scheduled according to their timezone.
    While Calendar manages the knighted correctly, there is a risk of confusion when the iPad (or iPhone) is set to automatically accept the location timezone. Switching the setting for time and calendar timezone support is a bit tedious.
    Is here a way to display the current timezone possibly in the top bar (next to the time), and also on the calendar page (since they timezones for displaying the time and managing calendar events is handled separately)?
    Would greatly help in reducing confusion about timings of events for frequent travelers.
    Cheers,
    Michael

    Hello,
    Did you found a solution for showing timezone in calendar?
    Thanks,

  • Ical misinterprets timezone in entourage meeting requests

    hi
    my timezone is GMT+8 and is set as such in Date & Time (10.4.7). I have Timezone support on in ICal Version 2.0.3 (1058). I also set the current timezone to asia/Singapore in ical. Meeting requests sent to me from Entourage which are also set to GMT + 8 turn up 8 hours late. The same meeting request however turns up at the correct time in outlook.
    I have included an example meeting request for reference:
    --B3242205558761762
    Content-Type: text/calendar;method=REQUEST;
    charset="US-ASCII";name="meeting.ics"
    Content-transfer-encoding: 7bit
    BEGIN:VCALENDAR
    VERSION:2.0
    PRODID:-//Microsoft Corporation//Entourage Mac 11.0 MIMEDIR//EN
    METHOD:REQUEST
    BEGIN:VTIMEZONE
    TZID:Kuala Lumpur, Singapore
    X-ENTOURAGE-TZID:40
    X-ENTOURAGE-CFTIMEZONE:Asia/Singapore
    BEGIN:STANDARD
    TZNAME:Standard Time
    TZOFFSETFROM:+0800
    TZOFFSETTO:+0800
    END:STANDARD
    END:VTIMEZONE
    BEGIN:VEVENT
    UID:F3A0C9FC-4DCF-11DB-BE7A-0016CB8D7BAA
    X-ENTOURAGE_UUID:F3A0C9FC-4DCF-11DB-BE7A-0016CB8D7BAA
    DTSTAMP:20060927T043900Z
    DTSTART;TZID="Kuala Lumpur, Singapore":20061004T093000
    DTEND;TZID="Kuala Lumpur, Singapore":20061004T110000
    LAST-MODIFIED:20060927T043900Z
    SUMMARY:......
    LOCATION:E1-5G
    ORGANIZER:MAILTO:....
    SEQUENCE:2
    ATTENDEE;ROLE=REQ-PARTICIPANT;RSVP=TRUE;CN="...
    X-MICROSOFT-CDO-BUSYSTATUS:BUSY
    X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
    X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
    X-MICROSOFT-CDO-INSTTYPE:0
    BEGIN:VALARM
    ACTION:DISPLAY
    DESCRIPTION:REMINDER
    TRIGGER;RELATED=START:-PT00H15M00S
    END:VALARM
    END:VEVENT
    END:VCALENDAR
    dual 1 GHz MD G4, 1.5 GIG RAM, 2T storage   Mac OS X (10.4.7)   Tascam 1884, cannopus advc110

    Hi- this did not help.
    I also have another example from Microsoft CDO for Microsoft Exchange. Still the same probelm- the alarm appears 8 hours late, despite the timezone being correct on both the sender's and receiver's machines.
    BEGIN:VCALENDAR
    METHOD:REQUEST
    PRODID:Microsoft CDO for Microsoft Exchange
    VERSION:2.0
    BEGIN:VTIMEZONE
    TZID:(GMT+08.00) Kuala Lumpur/Singapore
    X-MICROSOFT-CDO-TZID:21
    BEGIN:STANDARD
    DTSTART:16010101T000000
    TZOFFSETFROM:+0800
    TZOFFSETTO:+0800
    END:STANDARD
    BEGIN:DAYLIGHT
    DTSTART:16010101T000000
    TZOFFSETFROM:+0800
    TZOFFSETTO:+0800
    END:DAYLIGHT
    END:VTIMEZONE
    BEGIN:VEVENT
    DTSTAMP:20060928T065546Z
    DTSTART;TZID="(GMT+08.00) Kuala Lumpur/Singapore":20061003T103000
    SUMMARY:T204 ,,,,....
    UID:040000008200E00074C5B7101A82E00800000000A022A12D0EE3C601000000000000000
    ORGANIZER;CN="...
    LOCATION:...
    DTEND;TZID="(GMT+08.00) Kuala Lumpur/Singapore":20061003T133000
    DESCRIPTION:\N
    SEQUENCE:0
    PRIORITY:5
    CLASS:
    CREATED:20060928T065557Z
    LAST-MODIFIED:20060928T065558Z
    STATUS:CONFIRMED
    TRANSP:OPAQUE
    X-MICROSOFT-CDO-BUSYSTATUS:BUSY
    X-MICROSOFT-CDO-INSTTYPE:0
    X-MICROSOFT-CDO-INTENDEDSTATUS:BUSY
    X-MICROSOFT-CDO-ALLDAYEVENT:FALSE
    X-MICROSOFT-CDO-IMPORTANCE:1
    X-MICROSOFT-CDO-OWNERAPPTID:-1543727146
    X-MICROSOFT-CDO-APPT-SEQUENCE:0
    X-MICROSOFT-CDO-ATTENDEE-CRITICAL-CHANGE:20060928T065546Z
    X-MICROSOFT-CDO-OWNER-CRITICAL-CHANGE:20060928T065546Z
    BEGIN:VALARM
    ACTION:DISPLAY
    DESCRIPTION:REMINDER
    TRIGGER;RELATED=START:-PT00H15M00S
    END:VALARM
    END:VEVENT
    END:VCALENDAR

  • ICS Provided timezone converting incorrectly in iCal

    I'm attempting to use a CalDav data source and the source application timezone doesn't seem to be arriving in iCal correctly. For example, a timezone of "US/Eastern" in the source application appears as "Eastern Standard Time" in iCal. Syncing the same CalDAV calendar on my iPhone works correctly. Here is a sample of the ICS data that is coming across the network during a CalDAV sync.
    BEGIN:VCALENDAR
    VERSION:2.0
    CALSCALE:GREGORIAN
    PRODID:-//Starfield Technologies, Inc.//Stg GCal//3.1.09_caldav r7160//EN
    METHOD:REQUEST
    X-WR-CALNAME:Calendar
    X-APPLE-CALENDAR-COLOR:
    X-PUBLISHED-TTL:PT30M
    X-WR-CALDESCRIPTION:Calendar
    X-LIC-LOCATION:
    X-WR-TIMEZONE:
    BEGIN:VTIMEZONE
    TZID:US/Eastern
    BEGIN:STANDARD
    TZNAME:US/Eastern
    TZOFFSETFROM:-0500
    TZOFFSETTO:-0500
    DTSTART:19700101T000000
    END:STANDARD
    BEGIN:DAYLIGHT
    TZNAME:US/Eastern
    TZOFFSETFROM:-0500
    TZOFFSETTO:-0400
    DTSTART:19700101T000000
    END:DAYLIGHT
    END:VTIMEZONE
    BEGIN:VEVENT
    UID:daylighttime0000000001
    DTSTAMP:20100324T164601Z
    DTSTART;TZID=US/Eastern:20100330T120000
    DTEND;TZID=US/Eastern:20100330T123000
    SUMMARY:Daylight Time
    DESCRIPTION:
    LOCATION:
    SEQUENCE:0
    CREATED:20100324T164133Z
    LAST-MODIFIED:20100324T164133Z
    STATUS:CONFIRMED
    TRANSP:OPAQUE
    CLASS:PUBLIC
    END:VEVENT
    BEGIN:VEVENT
    UID:standardtime0000000001
    DTSTAMP:20100324T164601Z
    DTSTART;TZID=US/Eastern:20100302T120000
    DTEND;TZID=US/Eastern:20100302T123000
    SUMMARY:Standard Time
    DESCRIPTION:
    LOCATION:
    SEQUENCE:0
    CREATED:20100324T164239Z
    LAST-MODIFIED:20100324T164239Z
    STATUS:CONFIRMED
    TRANSP:OPAQUE
    CLASS:PUBLIC
    END:VEVENT
    END:VCALENDAR
    When syncing this into iCal with timezone support enabled and the timezone set to Mountain Standard Time these events show up at 10am (two hour offset) and should be 10am in standard and 9am in daylight. When iCal is set to Pacific time the events show up at 9am in standard and 10am in daylight when they should both be showing 9am.
    So, is this a problem with the ICS data that's coming across or iCal's interpretation of the timezone name? The fact that this same ICS data appears correctly on the iPhone and in Google's calendar leads me to believe that iCal is doing something incorrectly.

    I have experienced the same problem Seems to be a mail issue rather than an ical issue as any import into ical other than double clicking in mail (or automatically importing) works fine.  I have totally reinstalled OS 10.8 ( and dealth with the resulting challenges of getting everything synced back up again) and the problem has resurfaced within 24 hours
    Thanks for the drag and drop solution. I had been accepting on my iphone or ipad to avoid the issue.

  • ICal Time Zone Support functionality or workaround

    is there a third party or any workaround to the well-documented problem with traveling with an iPhone and using iCal?
    i don't want to get into all the details here but i would like to stay in the apple ecosystem for these items - in part because Mavericks iCal and Mavericks Reminders looks so awesome and with great looking added functionality.
    are there third party apps that work for folks?
    descriptions of workarounds that make iCal work for you with alerts at the correct time while traveling?
    THANKS

    suz..
    I just did the following and it seemed to correct the issue:
    - made sure my .me and iCal apps were set to the same timezone
    - turned off timezone support, closed iCal, turned timezone support back on
    - made sure i was not using 'floating timezone'
    that seemed to clear things up.

  • ICal time zone support

    Forgive me if this is repetitive. I do not regularly read these discussion groups. I've just noticed a little problem with iCal. We recently moved to another state and another time zone, specifically, from the Central to the Eastern time zone. Time Zone Support has always been clicked "on" in our iCal. Our iMac clock and time zone are set properly, to the Eastern time zone. I just noticed today that the iCal time zone on all my "events" is selected as "Central U.S." But they show up at all the correct times (i.e., Eastern U.S.) on iCal. Is this what Time Zone Support is supposed to do? Convert all the events to the time zone in which you are located? To add to my confusion, I just got an iPhone 3G, it's set to Eastern Time, and all the events synced from my at-home iCal show up one hour earlier than they should on the iPhone iCal. Any suggestions? Thank you!

    suz..
    I just did the following and it seemed to correct the issue:
    - made sure my .me and iCal apps were set to the same timezone
    - turned off timezone support, closed iCal, turned timezone support back on
    - made sure i was not using 'floating timezone'
    that seemed to clear things up.

  • Why 2 timezone settings in iOS?

    Perhaps more of a bug report/feature complaint than question, but why are there two separate places to set timezones?
    The general settings timezone is not recognized by calendar.
    There is a separate timezone settings in the calendar settings.
    Took me quite a while to find this after returning from a trip and having all my calendar still on the away timezone even though the General Settings timezone support showed I was home. Deep in the calendar settings, it still thought I was traveling.

    If you're talking about time zone support, this might help: http://support.apple.com/kb/HT4504.

  • Imported Timezone wrong

    I'm trying to import a calendar from Thunderbird-Lightening and iCal sets the timezone to +/-0 (Africa/O...) (It is +7 in the .ics file). I tried both with timezone support turned on and off. No Joy.
    Is this the problem I see complained about a lot on this group? Is there a solution or workaround?
    I'm only using iCal because I want to use iSync. Is there another, better, way?
    Thanks.

    I'm trying to import a calendar from Thunderbird-Lightening and iCal sets the timezone to +/-0 (Africa/O...) (It is +7 in the .ics file). I tried both with timezone support turned on and off. No Joy.
    Is this the problem I see complained about a lot on this group? Is there a solution or workaround?
    I'm only using iCal because I want to use iSync. Is there another, better, way?
    Thanks.

  • Getting current date and timestamp for timezone

    I am getting the current date and timestamp using
    Date d = new Date();
    On the platform I'm using it is returning it in GMT time.
    I want to convert this into Eastern Time Zone for United Status.

    java.util.Date objects contain a count of milliseconds since the "epoch", which happens to be midnight, Jan 1 1970 GMT. However, they aren't intrinsically "in" any timezone.
    If you simply call Date.toString(), you'll get the date formatted for the current locale, including timezone.
    If you want a different format, you can use the DateFormat or SimpleDateFormat classes (recommended), or use Calendar to pull the various date components out. You have to physically set the timezone for each of these.
    To get a list of timezones supported by your machine, you can run this program:
    import java.util.Arrays;
    import java.util.TimeZone;
    public class TZDump
        public static void main(String[] argv)
        throws Exception
            String[] zones = TimeZone.getAvailableIDs();
            Arrays.sort(zones);
            for (int ii = 0 ; ii < zones.length ; ii++)
                System.out.println(zones[ii]);
    }And, here's a program that lets you compare the same date in different timezones:
    import java.text.SimpleDateFormat;
    import java.util.Date;
    import java.util.TimeZone;
    public class TZDemo
        public static void main(String[] argv)
        throws Exception
            SimpleDateFormat fmt = new SimpleDateFormat("MM/dd/yy HH:mm:ss");
            Date now = new Date();
            System.out.println("Default TZ = " + fmt.format(now));
            String[] zones = new String[] { "EST", "EST5EDT", "PST"};
            for (int ii = 0 ; ii < zones.length ; ii++)
                fmt.setTimeZone(TimeZone.getTimeZone(zones[ii]));
                System.out.println("EST        = " + fmt.format(now));
    }

  • Automatic Timezone Weirdness

    Hi, my application is going to be accessed globally, across multiple timezones, and up until now I've not enabled automatic timezone support, and just clarified all my date labels saying "Date (GMT-6)", as my database is GMT-6.
    All my date fields have always been "timestamp with local timezone", and they've all displayed as say "19-JAN-2011 04:56 -06:00" (I'm using sysdate to update the time), and it's all worked solid and consistently, so long as you don't mind working out your local time using the offset displayed. In the database for that value, it stores "19-JAN-11 04.56.00.000000 AM" - ie. the local time to the DB.
    However, wanting to tidy up the app for the users, I've attempted to use automatic timezone support in my version - 4.0.2.
    It's my understanding that as I'm already using timestamp with local tz fields, all I should need to do is enable automatic timezone support, and it should work out the offset automatically, and display local times to my users. If I do this, all my timestamps set before I made the change display in the correct local time (ie. the time above is now shown as 19-JAN-2011 10:56 +00:00), but any subsequent times written display as the the GMT-6 time, but with a +00:00 timezone offset shown, and in the database are now stored with a -12 hours offset.
    I am in +00:00, my database is in -06:00, and so it looks like something somewhere applying the offset twice, and storing the time in the DB as -12:00, when it should be stored as -06:00 still, so it displays through the GUI correctly.
    Timezones confuse me at the best of times, can anyone help??

    This gets very strange - I've faked/changed my timezone to run some tests, and I've made subsequent timestamps a minute or two between each other, with different timezones, and can see the following dates/times stored in the DB:
    19-JAN-11 05.29.02.000000 AM     -06:00 test
    19-JAN-11 05.29.35.000000 AM     another -06:00 test
    19-JAN-11 06.30.48.000000 AM     -07:00 test
    18-JAN-11 11.32.04.000000 PM     GMT (+00:00) test
    19-JAN-11 07.34.34.000000 AM     -08:00 test
    Through the interface, if I'm on the same timezone as the database (-06:00), I see the times displayed as above. If I am on +00:00, I see the times above, but +6 hours. Very confusing, though I'm open to the possibility it's me being stupid... :)
    EDIT: On reading that, I get the impression the calculating and displaying of the offset and time is all working, it's the storing which isn't - ie. I'd expect to see all the times in the backend database showing in the same timezone, local to the DB, which they do when I don't have automatic timezone enabled.
    From the looks of it, it's applying the difference in offset to -06:00, the wrong way - ie. when UTC/GMT, 6 hours ahead of -06:00, it's subtracting that offset from the -06:00 time and storing that, making it -12:00 time in the DB. When in -07:00 timezone, (1 hour behind -06:00), it's adding that offset onto the -06:00 time and storing that.
    Edited by: TimS on Jan 19, 2011 11:59 AM

Maybe you are looking for