Linked Files in InDesign Now Modified after Daylight Savings Change

I looked for a discussion on this and couldn’t find one so if there is one already open please direct me to it and my apologies.
I was wondering if anyone else has run into this problem after the Daylight Savings Time Change on November 6th.
Starting on Monday, November 7th we have noticed that all of our InDesign files that had artwork files linked to the document are now coming up as being modified in the Links pallet even though that artwork has not been modified. I haven’t recalled having this issue since we were using Quark 4 and InDesign CS.
All files are stored on Windows servers running ExtremeZIP, all InDesign files are being opened on Mac Intel and Mac PowerPc models running either OSX 10.4 or OSX 10.6. All servers and Macs are sinc’d to pull the date and time from the same server and we verified that they are matching to the second.
We get the same results if the files are opened in InDesign CS4, CS5 or CS5.5.
Is anyone else seeing this issue and if so have you been able to rectify it without updating all the links and saving the files.
I’ve been searching everywhere and I have found tech notes from Adobe that states that this issue was fixed in CS4.0.6 but we are running this version and still suffering from the problem.
Any help would be appreciated.

This sounds like an ExtremeZIP bug. Like perhaps your server is not acconting for daylight saving properly in its on-the-wire protocol. I seem to recall there are a number of gotchas about this involving Windows. I would check with ExtremeZIP. Did the file dates/times change as shown by Get Info in the finder? I suppose it would be difficult to tell at this point...

Similar Messages

Citadel time wrong after daylight savings change

I have just noticed that all of my previous alarms in Citadel are now
off by 1 hour after the fall time change. For example, an alarm that
occured at 4:00 am yesterday (and was in the Citadel database as 4:00
am yesterday), is now shown as 3:00 am after the time change.
Any work arond for this? I am running lookout 6.0
Also, is there a way to change the order of the date field in Citadel?
It displays as month first in the date colum. I would like YYYYMMDD
HHMMSS so when I export to Excel it will sort corectly.
Thanks in advance.

alan,
What Bob said is correct. You can change the way Excel formats
the date to however you want by right-clicking on the cells and
selecting Format Cells..., then clicking on either Date, Time,
or Custom, and changing the format that way, however this will have no
bearing on how Excel sorts the columns. The values are stored in
Universal Time format.
Doug M
Applications Engineer
National Instruments
For those unfamiliar with NBC's The Office, my icon is NOT a picture of me

Alarm turned off after daylight savings change?

Hi. I woke up late this morning. I know I set my alarm last night. Last night was the change to daylight savings (forward one hour). Ok, I'm human, so of course being asleep, I can't be 100% sure I didn't turn it off without waking... we all have done that right? :P But I'm fairly certain I didn't, and am wondering if this may be a software glitch. I don't want to wait 6 months to find out when it changes back.
iPhone 4 fully updated. Alarm set to 5:30am

It seems that because of the structure and communication of Apple corporation, the Apple telephone support staff may not necessarily know any more than a thoughtful user, and almost certainly will know less about this particular alarm issue than a user who peruses these forums. For example, they didn't know that turning off Time Zone Support is another way to temporarily solve the problem (as an alternative to changing Set Automatically to OFF) - something I learnt from an Apple discussion.
This problem was raised in these discussions in June of this year for users in Lithuania and in Sri Lanka. It was New Zealand's turn in late September, and Australia's turn on Sunday. My guess is that Apple will scramble to fix the issue before it hits USA users in November, but why rush until then, when it's only users from other parts of the world (non-Americans) being affected?

Multiple instances spawned after daylight savings time change

This is a known issue and there is an SAP Knowledge Base Article created on this issue:
1448881 - Multiple instances spawned after daylight savings time change
Below is the information from the SAP Knowledge Base Article:
Symptom
Scheduled reports that are supposed to run once a day, run multiple times.
Duplicate instances are being created.
Environment
BusinessObjects Enterprise XIR2 SP5
BusinessObjects Enterprise XIR2 SP5 + FP5.x
Reproducing the Issue
A report is scheduled to be run on a daily basis - this is a Recurring schedule.
Normally the report runs once a day, at a particular time.
After Daylight Savings Time change, the report runs at the specified time, but immediately after the successful instance, another instance is spawned.
Many more instances spawn after each instance completes.
Cause
This is a known issue: ADAPT01318487. This issue is because of DST and how our code handles this change.
Resolution
There is currently no known fix for this issue. There is however a script that can quickly resolve the problem.
The issue it seems is related to Daily recurring schedules.
What this script will do:
it will run a query to display all your DAILY Recurring jobs
you will have the option to choose your jobs and reschedule them by 1 hour
you will then highlight the same job and change them back by 1 hour
by modifying the schedule times, you are modifying the schedule itself and this will keep the issue of duplicate instances from occurring.
Exact Steps to Complete:
Stop the Job Servers.
Double click on the .hta file.
Change the System Name to that of your CMS name.
Add the Administrator's password.
Click Logon.
Click List All Recurring Instances.
Select All.
Make note of what it says in: Schedule Selected Recurring Instances: Should be 1 hr earlier.
Click Reschedule Selected Recurring Instances.
Choose All instances again and change Schedule Selected Recurring Instances to 1 hour Later.
Click Reschedule Selected Recurring Instances.
Now start your Job Servers.
The issue should not occur again.
The Script is attached here, but please review the SAP Knowledge Base article 1448881 as well

Hi Nicola,
- The multiple spawned instances issue ONLY affects XI3 SP3+ only. For XI3 SP1 and SP2 all Fix Pack levels this is not an issue as it was introduced as a problem in SP3.
- 1568239 notes the Java version and can apply to all O/S environments and is updated to reflect that.
If you are located in Europe you can also apply the patches in advance of the DST change to avoid the problem. If you are in Americas at this point utilizing the clean up scripts for this year is the approach needed to clean up the spawned instances and reschedule the existing schedules.
Thanks,
Chris

Iphone calendar off by 1 hour after daylight savings

i have my iphone synced to my outook 2007 through an exchange server. after daylight savings this weekend, all of my appointments are now off by 1 hour. they are all correct in my outlook and on the exchange server (verified by web browser). i've tried deleting the exchange account from the phone and reinstalling, but that doesn't work. also, when i try adding a new appointment on my iphone, it shows up off by one hour in the exchange calendar. my iphone is currently showing the correct time.
anyone know what the heck is going on?

I also had success using this method, from above:
On iPhone, go to Settings>Mail, Contacts, Calendars.
Scroll way down to Time Zone Support. Note that it's listed as GMT-4. Turn slide button to OFF, then back to ON. Note that it automatically goes to Washington, DC (GMT-5).
Calendar appointment times now correct.
Time on the iPhone updated automatically for daylight savings, but the Time Zone Support function didn't make the one-hour shift; they ended up out by an hour from one another. Forcing Time Zone Support to refresh its settings was all that was needed.

Wrong timeshift of +1:00h after daylight savings activation

Since the change to daylight savings last Sunday, March 26th, the dates of files displayed in my Finder window are +1:00h newer than the corresponding reference files on my Linux-server. This holds only for files that were actually last modified between October 23rd and March 26th. Unfortunatley, this causes problems in the synchronization between the Linux-File-Server and my PowerBook (I am using ChronoSync). I think that my local Samba-client/Finder on my PowerBook has some intelligent that I would like to switch off. I would appreciate any help in this matter.
Thanks in advance and kind regards,
Joachim

jacky3brown, Welcome to the discussion area!
It sounds like the clock on the "Linux-server" did not make the daylight savings change.

All my calendar events moved back one hour after daylight savings

After daylight savings I noticed that all my calendar events are now showing one hour later. With an average of 10 events a day, there is no way to manually correct this- HELP!!!!! I was just one hour late to my first appointment of the day thanks to iCal and it's syncing to my iPhone.

OK, I did this. Then I closed iCal, then I reopened it. All my appts remain one hour late. Perhaps this will prevent this from happening during the next daylight change, I guess I will find out. "Time Zone support" to me implies that the time should be corrected if the computer moves to a new time zone.....
Irregarless. I've still got hundreds of appts showing an hour late, and as I enter more and more each day, it will become more and more confusing as to which ones are set to the correct time, and which ones are one hour late. How can I get all my appoints to show the correct time?????
HELP!

Calendar has wrong apt times after daylight savings

All of my calendar appointments are now off by 1 hr after daylight savings. I live in Arizona where we do not use daylight. How do I fix this.

jacky3brown, Welcome to the discussion area!
It sounds like the clock on the "Linux-server" did not make the daylight savings change.

Dreamweaver CS3 crashes after Daylight Savings Time ends

In Windows XP x64, Dreamweaver CS3 crashes after
Daylight Savings Time ends. There is a technote that seems to
describe the situation exactly.
http://kb.adobe.com/selfservice/viewContent.do?externalId=kb402776&sliceId=1
However...
1) The technote says this happens only with ASP and PHP code.
I'm using ColdFusion. (That's a minor point.)
2) The technote says...
Delete the WinFileCache-AD76BB20.dat file from the
Dreamweaver user configuration folder. Note that on Windows, the
Application Data and AppData folders are hidden by default, so
verify that your Windows Explorer folder options are set to View
Hidden Folders. The location of this file is as follows:
Dreamweaver CS3 on Windows Vista:
C:\Users\[username]\AppData\Roaming\Adobe\Dreamweaver
9\Configuration
Dreamweaver CS3 on Windows XP:
C:\Documents and Settings\[username]\Application
Data\Adobe\Dreamweaver 9\Configuration
However, I coudn't find WinFileCache-AD76BB20.dat in
Documents and Settings or in Program Files (86)\Adobe. (The 86 is
because this is a 32-bit program on a 64-bit machine, but all the
rest is the same.) I then searched both directories for *.dat and
there was no file that looked anything like
WinFileCache-AD76BB20.dat.
.Can anybody help me?
Thanks!

Alan, thanks for the suggestion.
I did the search found the file, deleted it, opened
Dreamweaver CS3, selected the same text -- and it crashed as
before.
THEN I REBOOTED and tried again - NO CRASH. So it seems that
a reboot is an essential part of the fix.
BTW: My situation fit the Technote description exactly. (1)
The crash happened when selecting -- in design or code view --
certain text in a context of HTML intermingled with ColdFusion
code; (2) I had no problem with these files before Daylight Savings
ended; (3) even after that I had no problem with them in Macromedia
Dreamweaver 8 on another machine -- the problem was only on CS3.
So the Technote is correct as far as it goes, but should be
amended as follows:
1) ColdFusion should be included in the types of code that
can be associated with the problem.
2) Instead of deleting WinFileCache-AD76BB20.dat, one should
delete WinFileCache-[whatever].dat.
3) A reboot after the deletion may be required.
Anyway, problem solved.
Thank you!

2007 US Daylight Savings change time zone support in JDK 1.3

Sun has supported the 2007 US Daylight Savings change in recent versions of its JDKs 1.4 and 1.5. It has made partial Daylight Savings changes to JDK 1.3, but it's not a complete implementation like in 1.4 and 1.5, because there is no support for past/future Daylight Savings rules, only a single current set of Daylight Savings rules per time zone.
Our Java application (running in the America/New_York time zone) seems to be doomed, because the likelihood of upgrading to JDK 1.4/1.5 seems slim (we have to upgrade a third-party product first and success is seeming more and more remote), and Sun claims to be unable to fully implement the Daylight Savings change in JDK 1.3.
If any Sun Java staff can explain the reasons for being unable to implement the change in 1.3 (or at least some kind of workaround that an individual JVM user could enable), please fill me in. Any pointers on cleanly setting up a custom workaround would be valuable too.
If there are other Java users in the same situation, please fill me in on your own plans if you can. Is anybody trying to pressure Sun or other vendors for a solution? Is anybody writing their own custom workaround?
More details....
What we really need is for the default TimeZone in JDK 1.3 (America/New_York on our machines) to work regardless of whether the date/time being checked is pre-2007 or post-2007. In particular, getOffset and inDaylightTime should work for both 2006 dates and 2007 dates. The JDK should return the correct values for 2006 dates, as well as the correct values for the 2007 US DST extension dates (03/12/2007-04/02/2007 and 10/29/2007-11/05/2007). This would enable parsing and formatting using SimpleDateFormat to work correctly as well. The TimeZone and SimpleDateFormat APIs are used throughout our application.
JDK 1.3.1_19 has an interesting workaround that depends on the current system time. Prior to Jan 1 2007, it will handle 2006 dates correctly but 2007 dates wrong. After Jan 1 2007, it will handle 2007 dates correctly but 2006 dates wrong. Either way, it is always wrong for some dates.
JDK 1.4.2_13 and 1.5.0_09 both handle 2006 and 2007 dates correctly.
If JDK 1.3 will never work for 2006 and 2007 dates, then I am contemplating two workarounds:
1. Set the default TimeZone to a custom implementation as soon after JVM startup as possible.
2. Avoid the default TimeZone entirely, changing our application code to rely on explicit custom TimeZones.
Prior related Java Forum topics:
* http://forum.java.sun.com/thread.jspa?forumID=31&threadID=645874 (Java Essentials - Java Programming) winds up referencing the JDK 1.4 patch as a solution, and there is some discussion about how future/historic dates affect applications
* http://forum.java.sun.com/thread.jspa?forumID=481&threadID=735038 (Deploying - Java Upgrade) just talks about 1.4 and 1.5 patches
* http://forum.java.sun.com/thread.jspa?forumID=481&threadID=717268 (Deploying - Java Upgrade) also just talks about 1.4 and 1.5 patches
* http://forum.java.sun.com/thread.jspa?forumID=37&threadID=703214 (Specifications - Java Virtual Machine (JVM)) also just talks about 1.4 and 1.5
Related Sun Java Bug Database bugs:
* http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6471271 reports the same issue with 1.3.1_19 that I am seeing and the reporter makes the same clarification, that past/future dates don't work at all still. Sun seems to indicate that it will not fix this in 1.3.1, and the 1.3.1_19 "hack" is it for 1.3.1.
* http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=6391777 refers to updates in 1.3.1_18 to address Australia DST changes, and also indicates that past/future dates (or "historic" dates) won't work at all. It gives a little more rationale behind the difficulty of implementing this for 1.3.1.
* http://bugs.sun.com/bugdatabase/view_bug.do?bug_id=4257314 refers to the fixes in 1.4 to support historic DST dates.
Other articles:
* Sun Java article http://java.sun.com/developer/technicalArticles/Intl/USDST/ refers to 1.3.1_18 as "resolving" the DST issue - this is misleading because the solution in 1.3.1_18 is not complete like that in 1.4 or 1.5
* Server Side article http://www.theserverside.com/news/thread.tss?thread_id=42212 refers to fixes in 1.4 and 1.5 for the DST issue, and the discussion about 1.3 doesn't lead anywhere
Thanks for any info or advice available,
Jim

Hi KBarney
I think u have the correct data file. to make sure see the "zi" dir is backed up in ur java lib folder or not.
if u have suspicion than run the tzupdater tool again.
this tool must be run for each jre/java version on your machine separately.
I tried this on 1.4.2.13 and not on 1.5.0.10. here is the result:
C:\Program Files\Java\j2re1.4.2_13\bin>java -jar c:\tzupdater\tzupdater2006p\tzu
pdater.jar -t -v
java.home: C:\Program Files\Java\j2re1.4.2_13
java.vendor: Sun Microsystems Inc.
java.version: 1.4.2_13
JRE time zone data version: tzdata2006p
Embedded time zone data version: tzdata2006p
Validating the time zone data
Validation complete
C:\tzupdater\tzupdater2006p>java -jar tzupdater.jar test verbose
java.home: C:\Program Files\Java\jre1.5.0_10
java.vendor: Sun Microsystems Inc.
java.version: 1.5.0_10
JRE time zone data version: tzdata2006k
Embedded time zone data version: tzdata2006p
Validating the time zone data
/data/tzdata2006p.test:990: test failed: America/Managua
/data/tzdata2006p.test:1465: test failed: America/Havana
/data/tzdata2006p.test:1466: test failed: America/Havana
/data/tzdata2006p.test:1847: test failed: Cuba
/data/tzdata2006p.test:1848: test failed: Cuba
/data/tzdata2006p.test:2024: test failed: America/Campo_Grande
/data/tzdata2006p.test:2026: test failed: America/Campo_Grande
/data/tzdata2006p.test:2028: test failed: America/Campo_Grande
/data/tzdata2006p.test:2030: test failed: America/Campo_Grande
/data/tzdata2006p.test:2032: test failed: America/Campo_Grande
/data/tzdata2006p.test:2034: test failed: America/Campo_Grande
/data/tzdata2006p.test:2036: test failed: America/Campo_Grande
/data/tzdata2006p.test:2038: test failed: America/Campo_Grande
/data/tzdata2006p.test:2040: test failed: America/Campo_Grande
/data/tzdata2006p.test:2046: test failed: America/Cuiaba
/data/tzdata2006p.test:2048: test failed: America/Cuiaba
/data/tzdata2006p.test:2050: test failed: America/Cuiaba
/data/tzdata2006p.test:2052: test failed: America/Cuiaba
/data/tzdata2006p.test:2054: test failed: America/Cuiaba
/data/tzdata2006p.test:2056: test failed: America/Cuiaba
/data/tzdata2006p.test:2058: test failed: America/Cuiaba
/data/tzdata2006p.test:2060: test failed: America/Cuiaba
/data/tzdata2006p.test:2062: test failed: America/Cuiaba
/data/tzdata2006p.test:2471: test failed: America/Montevideo
/data/tzdata2006p.test:2472: test failed: America/Montevideo
/data/tzdata2006p.test:2475: test failed: America/Montevideo
/data/tzdata2006p.test:2476: test failed: America/Montevideo
/data/tzdata2006p.test:2479: test failed: America/Montevideo
/data/tzdata2006p.test:2480: test failed: America/Montevideo
/data/tzdata2006p.test:2483: test failed: America/Montevideo
/data/tzdata2006p.test:2484: test failed: America/Montevideo
/data/tzdata2006p.test:2487: test failed: America/Montevideo
/data/tzdata2006p.test:2494: test failed: America/Sao_Paulo
/data/tzdata2006p.test:2496: test failed: America/Sao_Paulo
/data/tzdata2006p.test:2498: test failed: America/Sao_Paulo
/data/tzdata2006p.test:2500: test failed: America/Sao_Paulo
/data/tzdata2006p.test:2502: test failed: America/Sao_Paulo
/data/tzdata2006p.test:2504: test failed: America/Sao_Paulo
/data/tzdata2006p.test:2506: test failed: America/Sao_Paulo
/data/tzdata2006p.test:2508: test failed: America/Sao_Paulo
/data/tzdata2006p.test:2510: test failed: America/Sao_Paulo
/data/tzdata2006p.test:2516: test failed: BET
/data/tzdata2006p.test:2518: test failed: BET
/data/tzdata2006p.test:2520: test failed: BET
/data/tzdata2006p.test:2522: test failed: BET
/data/tzdata2006p.test:2524: test failed: BET
/data/tzdata2006p.test:2526: test failed: BET
/data/tzdata2006p.test:2528: test failed: BET
/data/tzdata2006p.test:2530: test failed: BET
/data/tzdata2006p.test:2532: test failed: BET
/data/tzdata2006p.test:2537: test failed: Brazil/East
/data/tzdata2006p.test:2539: test failed: Brazil/East
/data/tzdata2006p.test:2541: test failed: Brazil/East
/data/tzdata2006p.test:2543: test failed: Brazil/East
/data/tzdata2006p.test:2545: test failed: Brazil/East
/data/tzdata2006p.test:2547: test failed: Brazil/East
/data/tzdata2006p.test:2549: test failed: Brazil/East
/data/tzdata2006p.test:2551: test failed: Brazil/East
/data/tzdata2006p.test:2553: test failed: Brazil/East
/data/tzdata2006p.test:3451: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3452: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3453: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3454: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3455: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3456: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3457: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3458: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3459: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3460: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3461: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3462: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3463: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3464: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3465: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3466: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3467: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3468: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3469: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3470: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3471: time zone not found: Europe/Podgorica
/data/tzdata2006p.test:3791: test failed: ART
/data/tzdata2006p.test:3814: test failed: Africa/Cairo
/data/tzdata2006p.test:3844: test failed: Asia/Amman
/data/tzdata2006p.test:3848: test failed: Asia/Amman
/data/tzdata2006p.test:3852: test failed: Asia/Amman
/data/tzdata2006p.test:3856: test failed: Asia/Amman
/data/tzdata2006p.test:3860: test failed: Asia/Amman
/data/tzdata2006p.test:3887: test failed: Asia/Damascus
/data/tzdata2006p.test:3908: test failed: Asia/Gaza
/data/tzdata2006p.test:3911: test failed: Asia/Gaza
/data/tzdata2006p.test:3915: test failed: Asia/Gaza
/data/tzdata2006p.test:3919: test failed: Asia/Gaza
/data/tzdata2006p.test:3923: test failed: Asia/Gaza
/data/tzdata2006p.test:4035: test failed: Egypt
/data/tzdata2006p.test:4901: test failed: Australia/Perth
/data/tzdata2006p.test:4902: test failed: Australia/Perth
/data/tzdata2006p.test:4905: test failed: Australia/Perth
/data/tzdata2006p.test:4906: test failed: Australia/Perth
/data/tzdata2006p.test:4909: test failed: Australia/Perth
/data/tzdata2006p.test:4910: test failed: Australia/Perth
/data/tzdata2006p.test:4914: test failed: Australia/West
/data/tzdata2006p.test:4915: test failed: Australia/West
/data/tzdata2006p.test:4918: test failed: Australia/West
/data/tzdata2006p.test:4919: test failed: Australia/West
/data/tzdata2006p.test:4922: test failed: Australia/West
/data/tzdata2006p.test:4923: test failed: Australia/West
Validation tests failed.
-Ranjan

Daylight Savings Changes 2007

Daylight Savings time will be altered in 2007 as seen in http://geography.about.com/cs/daylightsavings/a/dst.htm
Is Coherence certified to handle these changes? We have already found issues in the OS and JDK that need to be patched.

Coherence will correctly handle daylight savings changes once the JDK has been patched.
Without the JDK patch, only the Coherence logging function will be incorrect, in that the logged messages will reflect the incorrect (unpatched) "timezone".
Coherence has very careful handling of "wall clock time" functionality to avoid being impacted by network time daemons, system clock irregularities, time zone shifts, etc.
Peace,
Cameron Purdy
Tangosol Coherence: Data Grid and Clustered Cache

Any imapct on MS JVM due to Daylight savings changes in 2007

Is there any imapct on MS JVM due to the Daylight savings changes in 2007.

I don't know. What did Microsoft support tell you when you asked them?

Linked Files in Indesign

I have Product Manuals I have to update all the time, 300 manuals. Is there a way to see if linked files in a InDesign file have been updated or broke in a file with out having to open every one of my files. The linked files that are in these manuals are revised and changed by other departments.
Thanks....

Hi,
You need to write a script to update the revised images automatically in InDesign without opening the application.
Thanks,
Praveen

How can I fix my calendar times? They are 1 hour early after daylight savings.

After my iPhone automatically changed to daylight savings times, it also made my calendar events 1 hour ealier than they should be. After checking threads I have double checked time zone support is on and matches my timezone in date and time. I sync with Outlook 2010 and the times are still correct here and I have tried to replace information on the iPhone with informqation from outlook, but this hasn't worked. Solutions?

Outlook (ver 2003 in my case but am sure many other versions...) and iPhone calendars cannot and will not share events with any degree of integrity regards their schedulling when synchronised via iTunes - specifically: events (recurring or otherwise) that are created PRIOR to a Daylight Savings Time event (in the UK our 2 events this year are March 25th and October 28th).
When transferred to the iPhone calendar during the sync process these events appear to be "altered" on all the incidences they appear AFTER a DST event and are displayed as either an hour ahead or behind their equivalent events within the Outlook calendar that they are supposed to be mirroring. iOS is effectively allocating these daylight-saved events a unique Time Zone of their own - this should NOT be happening.
Real life examples:
Weekly timed event (0900hrs-1100hrs) was created on February 5th to run every week until further notice... This displays correctly in Outlook for ALL instances - e.g. 0900hrs-1100hrs and irrespective of how far ahead you check the calendar... on iPhone calendar it displays correctly UNTIL March 25th - thereafter it is showing as timed at 1000hrs-1200hrs.This is massively frustrating... Changing the iPhone Time Zone from what should be the proper local "London" zone (in my case) to UTC I found cured the problem for these "orphans" when the clocks went back an hour last October - but this was a false cure and unfortunately many people discussing similar "cures" within these forums have not taken the trouble to examine the iPhone calendar in more detail and look either back to prev DST event date or forwards to the next DST event date because if they did they would find that all the calendar entries covering those periods will have been shifted by an hour.
One-off timed events - with or without alarms... These too get pushed forward an hour (post March 25th) - I missed a dentist appointment the other week because of this particular issue. I had actually planned the appointment months ago and at that time input it in iPhone calendar at the correct time/date. Outlook and/or the iPhone (or both in combination) somehow "marked" this appointment as a GMT appointment. When clocks went forward - this GMT "attribute" was preserved and applied to it - effectively the appointment was modified (without any authorisation/involvement on my part) and rescheduled to appear an hour later. Outrageous! Recurring alarmed events suffer same problem - with the alarms sounding an hour later of course.
I have tried all the so-called "fixes" to be found within these discussion groups and others all around the web and NONE have actually worked. Unfortunately, as I stated earlier, I suspect a lot of the reported "fixes" were premature annoucements from people who may not have their Outlook sync parameters set over a long enough time period for them to be able to view events several months ahead or behind and therefore see what happens to them AFTER the clock-change dates.
I need to determine which application is screwing this all up - is it Outlook or is it iOS? The fact of the matter is - I was able to use a Windows Mobile device that synced with Outlook 2003 for several years WITHOUT this issue. All that happened when DST event came along was the clock either went forwards or backwards - the events themselves were not interferred with and remained showing at the times they were originally set for - what could be simpler??
If I were planning to use the iPhone calendar on its own - without wanting to syncronise it with Outlook - I would not be here writing this post - but I purchased this device on the basis that Apple said it would be compatible with Outlook - it was a long thought-out decision as I was moving away from a Windows Mobile environment and ability to sync with Outlook was the only feature I needed to work.
The Outlook calendar sync feature is broken and has been for at least 3/4 years judging by the many reports to be found on the web. This needs fixing - NOW.

Why are my appointment off an hour after daylight savings time

After daykight savings time, my appointments are showing 1 hour early. I live in Arizona, isn,t my phone smart enough to know this and not adjust appointment times?

I fixed this problem by going to system preferences--mail, calendars--and turned off time zone support. When my iPhone didn't change time for daylight savings, i had changed the time manually and apparently this moved my time zone from SF to Anchorage. After disabling time zone support, all my appointments were correct. You can also disable tim zone support withon the iCal application on a mac.

Linked Files in InDesign Now Modified after Daylight Savings Change

Similar Messages

Maybe you are looking for