Task reminders and British Summer Time (GMT +1)

I have Ovi Suite 2.1.1.1 and an E71.
When I sync tasks with a reminder from Outlook, the reminder on my phone is one hour later. Schedule items sync at the right time.
I have selected GMT +1.00 on the phone as the time zone.
Something has obviously gone wrong with the timezone calculation as the phone doesn't realise that the time passed in from Outlook is already in British Summer Time (GMT +1) and goes ahead and adds an hour. However, it doesn't add an hour for schedule events....????
Ta,
Ed.

Yes, the same problem using a Nokia E72 in Hungary. Reminders in Outlook 2007 are 2 hours earlier than on the phone. Very irritating! I'm using OVI Suite 2.1.1.1 on Win 7 (64-bit).
Any help around?
Kristof

Similar Messages

British Summer Time - OSX 10.5.8 - time didn't change

Hi there,
British Summer Time is in effect as of last night, when all clocks were supposed to go forward an hour. The time on my iMac is set to update automatically, and has been doing so for the past 5 years...except today. It has remained at GMT, so I've had to change it manually. Changing the setting to 'auto' changes the time back one hour again.
I know Apple has had problems with daylight savings time on the iPhone...but haven't heard of any issues for OSX. Is there a fix for this?
Thanks.

My Iphone and Mac both messed up their time after British summer savings time came in -
Eventually I discovered that the mac had moved my timezone city location to Ghana in Africa; once I relocated to London the auto time on mac was fixed.
On the IPhone, I found that updating the ios to latest version fixed it.

British summer time solution in Apple Mail

Hi
Is there a solution to mail showing day light saving rather than British summer time.
The mail headers seem to be stamped with the correct time but the time received column in mail seems to add one hour, my system is set to the correct local time using the apple time server and local city is set to London.

> This has only become a problem since I moved from entourage to Mail.
Maybe you made the transition when the change to summer time took place, or maybe Entourage showed the sent date instead of the received date.
If you tell Mail to show the Date Sent column, the date will appear “correctly” there as well, but that’s because in that case it gets the date from the Date header instead of from the latest Received header...
so to clarify its our old quickmail server that is causing the problem?
Yes.
Do you no a work around
Not sure what you mean. The solution is obviously to set the date & time correctly on that computer (including the time zone & daylight saving settings). A work around could be moving the clock back one our again so that the time at least corresponds to the wrong timezone and Mail displays it correctly after converting it to the right timezone.

Do I need to worry about British Summer Time ?

As an example a simple 3 program chain job using a set up schedule which is set to run at 10:00 and 16:00 hours daily Mon-Sat
[repeat_interval   =>   'FREQ=daily; BYHOUR=10,16; BYDAY=mon,tue,wed,thu,fri,sat']
The default timezone is currently set to Europe/London.
Schedule start_time is set to TRUNC(systimestamp).
I would expect and want the job to kick off at the next instance of 10:00; then at 16:00 with this frequency being repeated daily whether we are in BST or not.
Based upon the above default_timezone and start_date settings, will the job run at 11:00 and 17:00 in BST (April to October) and revert to 10:00 and 16:00 (November to March) ?
If so, what are the default timesone settings to use and the correct start date
[E.G.: TRUNC(systimestamp); dbms_scheduler.stime() or something like To_TIMESTAMP_TZ('04-OCT-2010 10:00:00','DD-MON-YYYY HH24:MI:SS') ] which will allow the job to run correctly at 10:00 and 16:00 ?
Also what would happen to jobs which run over the changeover times from BST to non BST ?
Any help would be appreciated.

Thanks for the info. It has put me on the right track.
The key appears to be setting the timezone in both the scheduler default timezone AND in the start date (of the job or of the schedule if using a named schedule). All our jobs are run off named schedules so re-setting the start date does not affect running jobs and will only come into effect on the next job run. So re-setting can be done with no down time. Here are the results of my testing:
In order to prevent changes to scheduled times when BST cuts ober in March/October each year:
1.     set scheduler default timezone to Europe/London
2.     set job or schedule start date to include the default timezone.
     If this is not done, the correct scheduled run times will be dependent upon when the job is set up (in GMT or BST)
     I.E.      set up in GMT: times will be correct for GMT and 1 hour out in BST
          set up in BST: times will be correct for BST and 1 hour out in GMT
--check scheduler default timezone:
select DEFAULT_TIMEZONE from dba_scheduler_global_attribute;
Attribute_Name               Value
DEFAULT_TIMEZONE               Europe/London
cutover dates for 2010:
Sunday 28 March 01:00 GMT - Sunday 31 October 01:00 GMT (02:00 BST)
Results for cutover GMT to BST: Sunday 28 March 01:00
DECLARE
--set repeat interval
interval_string VARCHAR2(100) DEFAULT 'FREQ=DAILY;BYDAy=MON,TUE,WED,THU,FRI,SAT,SUN;BYHOUR=1,2,3,4,23,00';
start_date TIMESTAMP with time zone;
return_date_after TIMESTAMP with time zone;
next_run_date TIMESTAMP with time zone;
no_of_days PLS_INTEGER DEFAULT 40;
BEGIN
--set start_date to include timezone
--start_date           := to_timestamp_tz('25-MAR-2010 00:00:00 Europe/London' ,'DD-MON-YYYY HH24:MI:SS TZR');
--set start_date to NOT include timezone
start_date := to_timestamp_tz('25-MAR-2010 00:00:00' ,'DD-MON-YYYY HH24:MI:SS');
return_date_after := start_date;
FOR i IN 1..no_of_days LOOP
DBMS_SCHEDULER.EVALUATE_CALENDAR_STRING(
interval_string
,start_date
,return_date_after
,next_run_date);
DBMS_OUTPUT.PUT_LINE('next_run_date: ' ||to_char(next_run_date, 'DY DD-MON-YYYY HH24:MI:SS TZD TZH TZR'));
--DBMS_OUTPUT.PUT_LINE('next_run_date: ' ||to_char(next_run_date, 'DY DD-MON-YYYY HH24:MI:SS'));
return_date_after := next_run_date;
END LOOP;
END;
Result:
The offset is incorrect pre change at GMT (+01) and offset correct post change at BST (+01); resulting in times being 1 hour out;
resulting in times being 1 hour out.
next_run_date: THU 25-MAR-2010 01:00:00 +01 +01:00
next_run_date: THU 25-MAR-2010 02:00:00 +01 +01:00
next_run_date: THU 25-MAR-2010 03:00:00 +01 +01:00
next_run_date: THU 25-MAR-2010 04:00:00 +01 +01:00
next_run_date: THU 25-MAR-2010 23:00:00 +01 +01:00
next_run_date: FRI 26-MAR-2010 00:00:00 +01 +01:00
next_run_date: FRI 26-MAR-2010 01:00:00 +01 +01:00
next_run_date: FRI 26-MAR-2010 02:00:00 +01 +01:00
next_run_date: FRI 26-MAR-2010 03:00:00 +01 +01:00
next_run_date: FRI 26-MAR-2010 04:00:00 +01 +01:00
next_run_date: FRI 26-MAR-2010 23:00:00 +01 +01:00
next_run_date: SAT 27-MAR-2010 00:00:00 +01 +01:00
next_run_date: SAT 27-MAR-2010 01:00:00 +01 +01:00
next_run_date: SAT 27-MAR-2010 02:00:00 +01 +01:00
next_run_date: SAT 27-MAR-2010 03:00:00 +01 +01:00
next_run_date: SAT 27-MAR-2010 04:00:00 +01 +01:00
next_run_date: SAT 27-MAR-2010 23:00:00 +01 +01:00
next_run_date: SUN 28-MAR-2010 00:00:00 +01 +01:00
next_run_date: SUN 28-MAR-2010 01:00:00 +01 +01:00
next_run_date: SUN 28-MAR-2010 02:00:00 +01 +01:00
next_run_date: SUN 28-MAR-2010 03:00:00 +01 +01:00
next_run_date: SUN 28-MAR-2010 04:00:00 +01 +01:00
next_run_date: SUN 28-MAR-2010 23:00:00 +01 +01:00
next_run_date: MON 29-MAR-2010 00:00:00 +01 +01:00
next_run_date: MON 29-MAR-2010 01:00:00 +01 +01:00
next_run_date: MON 29-MAR-2010 02:00:00 +01 +01:00
next_run_date: MON 29-MAR-2010 03:00:00 +01 +01:00
next_run_date: MON 29-MAR-2010 04:00:00 +01 +01:00
next_run_date: MON 29-MAR-2010 23:00:00 +01 +01:00
next_run_date: TUE 30-MAR-2010 00:00:00 +01 +01:00
next_run_date: TUE 30-MAR-2010 01:00:00 +01 +01:00
next_run_date: TUE 30-MAR-2010 02:00:00 +01 +01:00
next_run_date: TUE 30-MAR-2010 03:00:00 +01 +01:00
next_run_date: TUE 30-MAR-2010 04:00:00 +01 +01:00
next_run_date: TUE 30-MAR-2010 23:00:00 +01 +01:00
next_run_date: WED 31-MAR-2010 00:00:00 +01 +01:00
next_run_date: WED 31-MAR-2010 01:00:00 +01 +01:00
next_run_date: WED 31-MAR-2010 02:00:00 +01 +01:00
next_run_date: WED 31-MAR-2010 03:00:00 +01 +01:00
next_run_date: WED 31-MAR-2010 04:00:00 +01 +01:00
Re-set start date to include timezone
I.E.:
start_date := to_timestamp_tz('25-MAR-2010 00:00:00 Europe/London' ,'DD-MON-YYYY HH24:MI:SS TZR');
The offset is correct pre change at GMT (+00) and offset correct post change at BST (+01); resulting in correct running times.
Note also the 1 hour jump on Sun 28th March from 00:00 to 02:00 which omits the 01:00 schedule which does not exist for that day.
next_run_date: THU 25-MAR-2010 01:00:00 GMT +00 EUROPE/LONDON
next_run_date: THU 25-MAR-2010 02:00:00 GMT +00 EUROPE/LONDON
next_run_date: THU 25-MAR-2010 03:00:00 GMT +00 EUROPE/LONDON
next_run_date: THU 25-MAR-2010 04:00:00 GMT +00 EUROPE/LONDON
next_run_date: THU 25-MAR-2010 23:00:00 GMT +00 EUROPE/LONDON
next_run_date: FRI 26-MAR-2010 00:00:00 GMT +00 EUROPE/LONDON
next_run_date: FRI 26-MAR-2010 01:00:00 GMT +00 EUROPE/LONDON
next_run_date: FRI 26-MAR-2010 02:00:00 GMT +00 EUROPE/LONDON
next_run_date: FRI 26-MAR-2010 03:00:00 GMT +00 EUROPE/LONDON
next_run_date: FRI 26-MAR-2010 04:00:00 GMT +00 EUROPE/LONDON
next_run_date: FRI 26-MAR-2010 23:00:00 GMT +00 EUROPE/LONDON
next_run_date: SAT 27-MAR-2010 00:00:00 GMT +00 EUROPE/LONDON
next_run_date: SAT 27-MAR-2010 01:00:00 GMT +00 EUROPE/LONDON
next_run_date: SAT 27-MAR-2010 02:00:00 GMT +00 EUROPE/LONDON
next_run_date: SAT 27-MAR-2010 03:00:00 GMT +00 EUROPE/LONDON
next_run_date: SAT 27-MAR-2010 04:00:00 GMT +00 EUROPE/LONDON
next_run_date: SAT 27-MAR-2010 23:00:00 GMT +00 EUROPE/LONDON
next_run_date: SUN 28-MAR-2010 00:00:00 GMT +00 EUROPE/LONDON
next_run_date: SUN 28-MAR-2010 02:00:00 BST +01 EUROPE/LONDON
next_run_date: SUN 28-MAR-2010 03:00:00 BST +01 EUROPE/LONDON
next_run_date: SUN 28-MAR-2010 04:00:00 BST +01 EUROPE/LONDON
next_run_date: SUN 28-MAR-2010 23:00:00 BST +01 EUROPE/LONDON
next_run_date: MON 29-MAR-2010 00:00:00 BST +01 EUROPE/LONDON
next_run_date: MON 29-MAR-2010 01:00:00 BST +01 EUROPE/LONDON
next_run_date: MON 29-MAR-2010 02:00:00 BST +01 EUROPE/LONDON
next_run_date: MON 29-MAR-2010 03:00:00 BST +01 EUROPE/LONDON
next_run_date: MON 29-MAR-2010 04:00:00 BST +01 EUROPE/LONDON
next_run_date: MON 29-MAR-2010 23:00:00 BST +01 EUROPE/LONDON
next_run_date: TUE 30-MAR-2010 00:00:00 BST +01 EUROPE/LONDON
next_run_date: TUE 30-MAR-2010 01:00:00 BST +01 EUROPE/LONDON
next_run_date: TUE 30-MAR-2010 02:00:00 BST +01 EUROPE/LONDON
next_run_date: TUE 30-MAR-2010 03:00:00 BST +01 EUROPE/LONDON
next_run_date: TUE 30-MAR-2010 04:00:00 BST +01 EUROPE/LONDON
next_run_date: TUE 30-MAR-2010 23:00:00 BST +01 EUROPE/LONDON
next_run_date: WED 31-MAR-2010 00:00:00 BST +01 EUROPE/LONDON
next_run_date: WED 31-MAR-2010 01:00:00 BST +01 EUROPE/LONDON
next_run_date: WED 31-MAR-2010 02:00:00 BST +01 EUROPE/LONDON
next_run_date: WED 31-MAR-2010 03:00:00 BST +01 EUROPE/LONDON
next_run_date: WED 31-MAR-2010 04:00:00 BST +01 EUROPE/LONDON
next_run_date: WED 31-MAR-2010 23:00:00 BST +01 EUROPE/LONDON
===============================================================================================
Results for cutover BST to GMT: Sunday 31 October 01:00 GMT (02:00 BST)
DECLARE
--set repeat interval
interval_string VARCHAR2(100) DEFAULT 'FREQ=DAILY;BYDAy=MON,TUE,WED,THU,FRI,SAT,SUN;BYHOUR=1,2,3,4,23,00';
start_date TIMESTAMP with time zone;
return_date_after TIMESTAMP with time zone;
next_run_date TIMESTAMP with time zone;
no_of_days PLS_INTEGER DEFAULT 40;
BEGIN
--set start_date to include timezone
--start_date            := to_timestamp_tz('27-OCT-2010 00:00:00 Europe/London' ,'DD-MON-YYYY HH24:MI:SS TZR');
--set start_date to NOT include timezone
start_date := to_timestamp_tz('27-OCT-2010 00:00:00' ,'DD-MON-YYYY HH24:MI:SS');
return_date_after := start_date;
FOR i IN 1..no_of_days LOOP
DBMS_SCHEDULER.EVALUATE_CALENDAR_STRING(
interval_string
,start_date
,return_date_after
,next_run_date);
DBMS_OUTPUT.PUT_LINE('next_run_date: ' ||to_char(next_run_date, 'DY DD-MON-YYYY HH24:MI:SS TZD TZH TZR'));
--DBMS_OUTPUT.PUT_LINE('next_run_date: ' ||to_char(next_run_date, 'DY DD-MON-YYYY HH24:MI:SS'));
return_date_after := next_run_date;
END LOOP;
END;
Result:
The offset is incorrect pre change at BST (+01) and offset correct post change at GMT (+01); resulting in times being 1 hour out;
resulting in times being 1 hour out.
next_run_date: WED 27-OCT-2010 01:00:00 +01 +01:00
next_run_date: WED 27-OCT-2010 02:00:00 +01 +01:00
next_run_date: WED 27-OCT-2010 03:00:00 +01 +01:00
next_run_date: WED 27-OCT-2010 04:00:00 +01 +01:00
next_run_date: WED 27-OCT-2010 23:00:00 +01 +01:00
next_run_date: THU 28-OCT-2010 00:00:00 +01 +01:00
next_run_date: THU 28-OCT-2010 01:00:00 +01 +01:00
next_run_date: THU 28-OCT-2010 02:00:00 +01 +01:00
next_run_date: THU 28-OCT-2010 03:00:00 +01 +01:00
next_run_date: THU 28-OCT-2010 04:00:00 +01 +01:00
next_run_date: THU 28-OCT-2010 23:00:00 +01 +01:00
next_run_date: FRI 29-OCT-2010 00:00:00 +01 +01:00
next_run_date: FRI 29-OCT-2010 01:00:00 +01 +01:00
next_run_date: FRI 29-OCT-2010 02:00:00 +01 +01:00
next_run_date: FRI 29-OCT-2010 03:00:00 +01 +01:00
next_run_date: FRI 29-OCT-2010 04:00:00 +01 +01:00
next_run_date: FRI 29-OCT-2010 23:00:00 +01 +01:00
next_run_date: SAT 30-OCT-2010 00:00:00 +01 +01:00
next_run_date: SAT 30-OCT-2010 01:00:00 +01 +01:00
next_run_date: SAT 30-OCT-2010 02:00:00 +01 +01:00
next_run_date: SAT 30-OCT-2010 03:00:00 +01 +01:00
next_run_date: SAT 30-OCT-2010 04:00:00 +01 +01:00
next_run_date: SAT 30-OCT-2010 23:00:00 +01 +01:00
next_run_date: SUN 31-OCT-2010 00:00:00 +01 +01:00
next_run_date: SUN 31-OCT-2010 01:00:00 +01 +01:00
next_run_date: SUN 31-OCT-2010 02:00:00 +01 +01:00
next_run_date: SUN 31-OCT-2010 03:00:00 +01 +01:00
next_run_date: SUN 31-OCT-2010 04:00:00 +01 +01:00
next_run_date: SUN 31-OCT-2010 23:00:00 +01 +01:00
next_run_date: MON 01-NOV-2010 00:00:00 +01 +01:00
next_run_date: MON 01-NOV-2010 01:00:00 +01 +01:00
next_run_date: MON 01-NOV-2010 02:00:00 +01 +01:00
next_run_date: MON 01-NOV-2010 03:00:00 +01 +01:00
next_run_date: MON 01-NOV-2010 04:00:00 +01 +01:00
next_run_date: MON 01-NOV-2010 23:00:00 +01 +01:00
next_run_date: TUE 02-NOV-2010 00:00:00 +01 +01:00
next_run_date: TUE 02-NOV-2010 01:00:00 +01 +01:00
next_run_date: TUE 02-NOV-2010 02:00:00 +01 +01:00
next_run_date: TUE 02-NOV-2010 03:00:00 +01 +01:00
next_run_date: TUE 02-NOV-2010 04:00:00 +01 +01:00
Re-set start date to include timezone
I.E.:
start_date := to_timestamp_tz('27-OCT-2010 00:00:00 Europe/London' ,'DD-MON-YYYY HH24:MI:SS TZR');
The offset is correct pre change at BST (+00) and offset correct post change at GMT (+01); resulting in correct running times.
Note: no one hour jump on Sun 31st Oct
next_run_date: WED 27-OCT-2010 01:00:00 BST +01 EUROPE/LONDON
next_run_date: WED 27-OCT-2010 02:00:00 BST +01 EUROPE/LONDON
next_run_date: WED 27-OCT-2010 03:00:00 BST +01 EUROPE/LONDON
next_run_date: WED 27-OCT-2010 04:00:00 BST +01 EUROPE/LONDON
next_run_date: WED 27-OCT-2010 23:00:00 BST +01 EUROPE/LONDON
next_run_date: THU 28-OCT-2010 00:00:00 BST +01 EUROPE/LONDON
next_run_date: THU 28-OCT-2010 01:00:00 BST +01 EUROPE/LONDON
next_run_date: THU 28-OCT-2010 02:00:00 BST +01 EUROPE/LONDON
next_run_date: THU 28-OCT-2010 03:00:00 BST +01 EUROPE/LONDON
next_run_date: THU 28-OCT-2010 04:00:00 BST +01 EUROPE/LONDON
next_run_date: THU 28-OCT-2010 23:00:00 BST +01 EUROPE/LONDON
next_run_date: FRI 29-OCT-2010 00:00:00 BST +01 EUROPE/LONDON
next_run_date: FRI 29-OCT-2010 01:00:00 BST +01 EUROPE/LONDON
next_run_date: FRI 29-OCT-2010 02:00:00 BST +01 EUROPE/LONDON
next_run_date: FRI 29-OCT-2010 03:00:00 BST +01 EUROPE/LONDON
next_run_date: FRI 29-OCT-2010 04:00:00 BST +01 EUROPE/LONDON
next_run_date: FRI 29-OCT-2010 23:00:00 BST +01 EUROPE/LONDON
next_run_date: SAT 30-OCT-2010 00:00:00 BST +01 EUROPE/LONDON
next_run_date: SAT 30-OCT-2010 01:00:00 BST +01 EUROPE/LONDON
next_run_date: SAT 30-OCT-2010 02:00:00 BST +01 EUROPE/LONDON
next_run_date: SAT 30-OCT-2010 03:00:00 BST +01 EUROPE/LONDON
next_run_date: SAT 30-OCT-2010 04:00:00 BST +01 EUROPE/LONDON
next_run_date: SAT 30-OCT-2010 23:00:00 BST +01 EUROPE/LONDON
next_run_date: SUN 31-OCT-2010 00:00:00 BST +01 EUROPE/LONDON
next_run_date: SUN 31-OCT-2010 01:00:00 GMT +00 EUROPE/LONDON
next_run_date: SUN 31-OCT-2010 02:00:00 GMT +00 EUROPE/LONDON
next_run_date: SUN 31-OCT-2010 03:00:00 GMT +00 EUROPE/LONDON
next_run_date: SUN 31-OCT-2010 04:00:00 GMT +00 EUROPE/LONDON
next_run_date: SUN 31-OCT-2010 23:00:00 GMT +00 EUROPE/LONDON
next_run_date: MON 01-NOV-2010 00:00:00 GMT +00 EUROPE/LONDON
next_run_date: MON 01-NOV-2010 01:00:00 GMT +00 EUROPE/LONDON
next_run_date: MON 01-NOV-2010 02:00:00 GMT +00 EUROPE/LONDON
next_run_date: MON 01-NOV-2010 03:00:00 GMT +00 EUROPE/LONDON
next_run_date: MON 01-NOV-2010 04:00:00 GMT +00 EUROPE/LONDON
next_run_date: MON 01-NOV-2010 23:00:00 GMT +00 EUROPE/LONDON
next_run_date: TUE 02-NOV-2010 00:00:00 GMT +00 EUROPE/LONDON
next_run_date: TUE 02-NOV-2010 01:00:00 GMT +00 EUROPE/LONDON
next_run_date: TUE 02-NOV-2010 02:00:00 GMT +00 EUROPE/LONDON
next_run_date: TUE 02-NOV-2010 03:00:00 GMT +00 EUROPE/LONDON
next_run_date: TUE 02-NOV-2010 04:00:00 GMT +00 EUROPE/LONDON
I created a little function to return the start date I want. The IN parameter is defaulted to NULL which will default to today:
CREATE OR REPLACE FUNCTION get_start_date_with_timezone(p_start IN VARCHAR2 DEFAULT NULL)
RETURN timestamp with time zone
IS
w_check timestamp;
w_return timestamp with time zone;
BEGIN
IF p_start IS NOT NULL
THEN
--check if p_start is a valid date
w_check := to_date(p_start, 'dd-mon-yyyy');
--if you get here it is a valid date
w_return := to_timestamp_tz(p_start||' 00:00:00 Europe/London' ,'DD-MON-YYYY HH24:MI:SS TZR');
ELSE
--set to midnight this morning
w_return := to_timestamp_tz(to_char(TRUNC(systimestamp), 'dd-mon-yyyy hh24:mi:ss')||'Europe/London' ,'DD-MON-YYYY HH24:MI:SS TZR');
END IF;
RETURN(w_return);
EXCEPTION
WHEN OTHERS
THEN
RAISE;
END;
I'll use this function in a cursor for loop through dba_scheduler_schedules for the users I want using the dbms_scheduler.set_attribute.
Thanks once again.

British Summer TIme problem

I've linked iCal with MobileMe. However, if I enter a recurring weekly 10am appointment starting in February, after the end of March it displays it in Monthly view as 11am, even though in edit view for that date it shows 10am. Anybody know the solution? Kev

its not a BST problem its a general sumer/winter time thing
Ive put in a lot of entries in PST as I have to do things based on that time zone, but Im on CET/CEST. Time zone support is on and so far so good, but, last night the clocks went forward, and all the appointments made on PST are shown incorrectly now in CEST (i.e. they are 1 hour late).
iCal does not take into account time changes within a time zone. All the appointments I enter now in PST are incorrect in CEST.
Any fixes ?

How to detect Summer Time change (GMT or GMT+1)

Hi all,
My problem is that I retrieve from xml a timestamp. It indicates the London local hour.
I do format the Calendar constructed object with SimpleDateFormat, but I have to append "GMT" or "GMT+1" (BST) to the output String.
How do I detect when the time is BST (British Summer Time) and when Greenwich Mean Time?
Thanks for your help.
Best regards,
Antonio

Hello Jarrod
Thank you for your help, I looked the previous threads and download .NET Framework 2.0. Finally I am able to get it work.
Amit

Dreamweaver, summer time, and synchronisation

One of the minor but irritating and recurrent problems with
Dreamweaver's synchronise function is that, after a change to/from
British Summer Time (Daylight Saving Time for those of you across
the Pond), any synchronise operation will inform you that the file
on the server has changed since the last synchronisation and ask
you what you want to do, even when the file is plainly the same.
You can tell that it's a BST problem because the timestamp differs
by exactly one hour. I'm guessing that the synch info is stored in
the _notes/dwsync.xml in each directory. So my Q is: how can I
reset all synch info for a site? Searching for "synch" in the fine
help file returns nothing useful.
This isn't something I want to spend any time on as it's
relatively trivial, but it is annoying and renders the synch
feature semi-useless until I manually synch all files in a site,
and can also lead to wrong up/downloads with the danger of
overwriting later versions. I'm using DW CS3 (aka v9) under Windows
eXtra Pathetic. TIA for any tips.
Cheers
Fred

I'm having the same problem and its about time Adobe sorted it. Still trying to work out if its a Mac client with windows server problem. Is there a way to notify Adobe without spending my life on the phone? Using CS5.5 and FTP over TLS/SSL Explicit connection

NX-OS - clock summer-time - Last sunday for BST?

Hiya,
This may be a dumb question - I may just be missing something obvious - but I'm trying to setup some NX-OS based devices (5548Ps/5020s/1000Vs) with the correct daylight savings setting for the UK - ie. british summer time.
The definition of BST is:
"British Summer Time (BST) starts on the last Sunday in March and ends on the last Sunday in October, at 1.00 am Greenwich Mean Time (GMT)"
ie. it's always the 'last' sunday'. On our IOS devices we do this:
clock timezone GMT 0
clock summer-time BST recurring last Sun Mar 1:00 last Sun Oct 1:00
....but there's no equivalent 'last' keyword on NX-OS:
clock summer-time zone-name start-week start-day start-month start-time end-week end-day end-month end-time offset-minutes
Sometimes the 'last' sunday is the 4th, and sometimes it's the 5th...?
Anyone know how to set it to the last sunday? Or do I just have to accept it's sometimes going to be a week out?
Thanks,
Rob...

Looks like you're right Jerry! Thanks!
Just managed to find a switch to test it on - and it works as expected:
switch-n5k(config)# sh run | inc clock
clock timezone GMT 0 0
clock summer-time BST 5 Sunday March 01:00 5 Sun Oct 01:00 60
switch-n5k(config)# sh clock
00:56:38.908 GMT Sun Mar 27 2011
switch-n5k(config)# sh clock
02:02:59.779 BST Sun Mar 27 2011
switch-5k(config)#
Thanks,
Rob...

IdM Scheduler and Time Change to Daylight Savings Time GMT to BST

This isn't really a 'question' , but just a topic for discussion.
We're not live yet, but will be by the time the clocks go back. So I'm just interest to hear everyone's experiences and any issues with regards to the switching to / from DST
I did some "interesting" (or not) tests last night to see what happens with Pending Values which are due to take effect at the time change threshold of 01:00 GMT when switching to Daylight Savings Time (BST) GMT +0100.
It seems as if the IdM scheduler keeps going according to UTC or GMT. However any values provisioned to target systems or to local tables using the ddm.datetime8601 system variable are in local time according to the runtime server or SQL server's locale settings.
I set up a task to output from a javascript the current system date
using the following in the functions.
currentTime = new Date();
return currentTime.toString(); // returns Locale Time String
currentTime = new Date();
return currentTime.toUTCString(); // returns UTC Time String
in the same pass I also output the ddm.datetime8601 system parameter and the ddm.time24 system parameter.
This task was to update a comment on an entry and Scheduled to run at 00:00:00 and was executed at 00:00:06 GMT all times were still in GMT as expected.
Local Time: Sun Mar 27 00:00:06 GMT-0000 (GMT) 2011, UTC Time: Sun, 27 Mar 2011 00:00:06 GMT, ddm.datetime8601: 2011-03-27T00:00:06, ddm.time24: 00:00:06
This task was scheduled at 01:00:00 in IdM and was exectued at 01:00:08 GMT by the runtime, and you can see the local time is being correctly reported as 02:00:08 BST. Note also the ddmdatetime8061 is also 02:00:08 i.e. BST.
Local Time: Sun Mar 27 02:00:08 GMT+0100 (BST) 2011, UTC Time: Sun, 27 Mar 2011 01:00:08 GMT, ddm.datetime8601: 2011-03-27T02:00:08, ddm.time24: 02:00:08
In the database the entry values MXI_VALUES ModifyTime field has the GMT / UTC timestamp.
I also set up some pending value objects to be applied at 00:59:59 and 01:30:00 to see if the 01:30:00 would be 'skipped' as the locl clock change would've gone from 00:59:59 to 02:00:00. Well the pending values were correctly applied and expired and no 'lost' transactions happened as a result of the change.
So essentially it seems to me that the IdM runtime and scheduler times are all based on UTC / GMT.
I guess it's only an issue twice a year if you're expecting something to happen at a specific local time 01:00:00 or if you've got a global user base and their account expiry should be in each user's own country's local time. In these cases, it would seem that you'd need to convert the schedule times and pending value times to UTC first before setting them in the database.
Has anyone else had any issues, thoughts, questions or suggestioins on scheduling tasks which span the DST time change when switching to and from Daylight Savings Time.
Edited by: Paul Abrahamson on Mar 27, 2011 10:51 AM

Read here:
http://www.appleinsider.com/articles/10/10/11/applesays_ios_software_update_to_fix_pesky_alarm_clockbug.html

Every time i close firefox, to re-open it i have to either log out and log back in, or i have to go through the task manager and end the proccess, otherwise it just says fire fox if already running and it wont open, how do i fix this proble??

Everytime i am finished using Firefox, if i want to go back onto the internet, i now have to either log off and then log back on. or i have to use the task manager and close the firefox process, it is extrlmely annoying as i have to do it everytime, if i try and open firefor before i do either of what i have explained it just comes up with, firefox is allready running please close all windows to open a new one, or end the process...how do i stop this message from popping up every single time i use firefox????

https://support.mozilla.com/en-US/kb/Firefox+hangs#Hang_at_exit

Having problems opening firefox (vista) i have to goto task manager and close process all the time just to reopen?

hi i have just recentley started having problems opening firefox up (before update) i use vista, i can double click on icon and nothing happens but when i turn pc off it pops up as the screen is going off very strange? the only way i can get it to work is by going in to task manager and ending firefox process yet there isnt firefox running????

yea thanks thats the issue there is nothing in applications for firefox so i cant close anything there but in processes there is Firefox.exe useing 30,000k so i close that, but im even stuggling with that now to get firefox working now i just had to do that process around 10 times!!!!! and then only with right clicking firefox in start menu

Time in iCal are US (EST) but sync to MobileMe and iPhone as UK (GMT)

Time in iCal are US (EST) but sync to MobileMe and iPhone as UK (GMT). How can I correct this? I thought I had changed all my settings after I got back from the UK.
Any help would be great.
Thanks.

Sorry, I re-read this and realized that my explanation of the problem may not have been clear. (I need to get more sleep)
When I add a new event into iCal on my Mac it shows up at 1:45pm EST. When the event syncs via MobileMe it shows up as 6:45pm (18:45) on my iPhone and in MobileMe online. How can I get the events to shows up at the correct time (1:45pm) on my iPhone and online?
Thanks

Since installing fox4 every time i close and reopen i have to go to task mgr and end fox process this works sometimes other time fox wont open asnd i have to reboot pc this is bad

after installing f/fox 4 if i close itdown i get message f/fox is still running i have to go to task mgr and end fox process sometimes this doesnt work i then have to reboot pc this is very annoying
any ideas ? rgds con

https://support.mozilla.com/en-US/kb/Firefox+hangs#Hang_at_exit

Odd clock drift since summer time clock change

This is a weird one. Since the clocks changed back for daylight savings time (here in the UK, on Sunday morning from BST to GMT) I've been getting a strange error: while I'm editing a file in vi(1), occasionally when I come to save it tells me the file has changed on disk (it hasn't).
I thought I was going mad until a colleague said he's seen the same warnings on his machine in Eclipse. It seems to me like the clock is constantly drifting/being adjusted - I'm syncing with NTP to time.euro.apple.com, and I am seeing a lot of NTP updates in the logs:
system.log:Nov 2 19:18:26 mightymac ntpd[34353]: time reset +0.280424 s
system.log:Nov 2 20:26:10 mightymac ntpd[34353]: time reset -0.857206 s
system.log:Nov 2 20:26:10 mightymac ntpd[34353]: frequency error -589 PPM exceeds tolerance 500 PPM
system.log:Nov 2 21:01:15 mightymac ntpd[34353]: time reset +0.974976 s
system.log:Nov 2 23:00:28 mightymac ntpd[34353]: time reset +0.557037 s
system.log:Nov 2 23:34:56 mightymac ntpd[34353]: time reset +0.960510 s
system.log:Nov 3 09:49:37 mightymac ntpd[34353]: time reset -1.004375 s
system.log:Nov 3 10:07:17 mightymac ntpd[34353]: time reset +0.491741 s
These are big jumps - a second, half a second, much more than I'd expect to see. Given it's happening on a colleagues machine we can rule out my clock battery or other local hardware/software issues, it's happening both when I'm at work and at home (on two different networks), and it's only happening since the summer time change on Sunday.
Has anyone else seen this? This is on 10.6.4, on two machines that have not been rebooted since the clocks changed.

I have a similar problem - when I start up my clock has advanced about 13 hours. It seems to have been doing this since daylight savings changed. It has the right time zone and I have unlinked synchronisation but it keeps happening even when it is locked.

Outlook Task reminders sync incorrectly

My phone is synced to our mail server thru exchange 2013. When I create a task in outlook and put a reminder time it shows in outlook correctly. Once the task syncs to my iphone5 everything is correct but the reminder time. It always defaults to 12am. You have to open the task on the phone and correct it.
But...
If you create a task on the phone first it syncs correctly to outlook. Correct reminder time and everything.
is this just a bug with the phone, exchange or is there something i can tweak to resolve this.

Any help on this guys?
Driving my users and myself nuts - not having task reminders go off at the correct time.
cheers.

Task reminders and British Summer Time (GMT +1)

Similar Messages

Maybe you are looking for