I am not sure if it is a VZW or a WM issue but coming over from the i760, would the TP2 give me the ability to handle time zone change better? The i760 never did let me update local time without changing to local time zone as well. My old Treo 650 could even do that. I travel a lot and dont want all my Exchange server driven calendar items to go bouncing around according to time zone change. But I do want auto update to local time. So will the TP2 do that for me? TIA...

I don't travel as much as you probably, but why wouldn't you want your appointments to match the timezone you are in? If you are in central time, don't you want your appointments to show up.

If the local time is noon, wouldn't you want the appointment on your device to say noon as well?

I'm not being critical or anything, just wondering how you want it to work.

I do travel a lot, and used to keep everything in "local" time. A few months ago, I made the leap to "universal" time. It is a huge improvement, although it takes a little getting used to.

An example will illustrate how this works. I am in California and scheduling a meeting next week when I will be in New York at 8am EST. In the "local" method, I enter 8am into the calendar. In "universal" time, I enter the meeting at 5am because I am currently in PST.

When I travel, my phone updates. Now the 5am appointment shows at 8am and everything works fine. If I used "local" time, I would have to prevent my phone from updating its timezone.

The real rub comes with multi-timezone computer scheduling, e.g. initations in outlook. These are generally done in "universal" time. And if daylight savings time starts / ends the computer just tracks them.

So in response to poster #1, my suggestion is to adopt the "universal" approach to calendaring and let your appointments jump all over. Then they will always be correct.

My two cents.

David

Thanks for the responses. There are other posts about this problem and it is a clear case of problem on either the WM end or 760 end. I have been working for two years to solve. Sounds like if I stay with a WM phone I cannot solve this prob. The universal solution doesn't work for me. The reason is that while still in CA I want to be able to look at my cal and know the meeting is at 8AM not 5AM. If you look on the 760 go phone/options/services/time you get to the screen where you SHOULD be able to fix this. You SHOULD be able to set time to "auto" and see the phone update everytime your plane lands. You SHOULD also be able to se time zone to "manual" and not see any of your calendar items jump around as you change time zones. That way theoretically you could set all cal items for local time and everything stays stable. My old Palm OS Treo 650 did this effortlessly but with WM and i760 it does NOT work. I have called VZW support and been given an apology and admission that it does not work so I suspect VZW. I am considering the TP2 as a new phone but not if this issue is not fixed.

I've had the same challenges. It seems that by trying to do less with time synchronization, the old phones were easier to use for the "local" time method.

Your point about glancing at a "local" calendar while in CA and seeing that the meeting is at 8 local and not 5 is a good one. I use outlook for a lot of my calendaring, and frequently display multiple timezone scales to deal with this issue. On my phone, I am usually responding to the truely local situation (e.g. I am in New York and where I am supposed to be now) rather than longer-range planning.

If your plans change unexpectedly, the 8 / 5 issue above is actually a feature. More than once I have had flights change and find myself taking a call from a different time zone than I originally planned. In this case, the 5am meeting time is actually correct!

I think time zone complications are a matter of chosing where you want difficulty. In the "universal" method, you rely on the computers to make the adjustments and conversions. But you have to keep track of what a "5am" appointment means in NY when you are in CA. In the "local" method, you need to convert times based on your planned locations and adjust. You get to pick.

As I said, I used to use the "local" method, then finally gave myself over to the "universal" method. It takes some getting used to, but I would not go back -- I make fewer mistakes now and overall it takes less effort for me.

David

I'd have to agree, I live a few miles from the time zone line, and commonly cross it for work, its truly a blessing for me that the phone handles it all.

three west how is it that your phone "handles it all" are you saying you have found a way to keep calendar items stable while local time stays accurate?

naw, they're always accurate to the time zone that I'm in, and I like it that way. No math, accurate reminders, etc.

I guess the universal time approach is better because you can handle it in your office beforehand, instead of trying to correct all your appointments on the fly as you run from meeting to meeting at a conference --- but still it's a pain in the butt!