10-08-2013 03:46 AM
I have a BB Bold 9900
I am using desktop software 220.127.116.11 Bundle 42
When i sync to my phone all goes ok. When I resync both ways it corrupts calendar entries.
Specifically if I:
1.Change an appointment on my phone it corrupts it on outlook. For exemple I thake an appointment on the phone and change time appointment from 8:30-9:00 to 9:00-10:00 When i search for it on outlook the end time is before the start time andit is corrupt. Shows as appontment from 9:00-8:30 on outlook.
2. If I dismiss an item on phone. on next sync it deletes from outlook.
I have tried
- deleting all calender items and resyncing - same problem.
- checked time zones - both PC & BB set to GMT +2 (South Africa)
I have been using BB & Sync for 5 years now and have never had such issues I cannot resolve.
I have just got a new notebook and this error is persisting.
please can you assist.
10-16-2013 04:01 AM
Time issues on Appointments Sync
BB Bold 9900
BB Software Version: 7.1 Bundle 2061 (v18.104.22.1684, Platform 22.214.171.1242)
Desktop Software 126.96.36.199 Bundle 42
I reset everything, deleted data from BB and started from scratch. I synced all one way to phone and all was correct and synced properly.
I then changed nothing and did a 2 way sync. It reported changes on every calendar item. Time in phone = 8:00 time in Outlook = 9:00. Outlook is correct and BB is 9:00 when you view the appointment. If I continue it changes with accept Outlook as correct it changes the time on the phone to 10:00.
When I then changed appointment on BB to be from 09:00 to 09:30 and resynced. It then shows the appointment on BB as being from 10:00 to 9:30 the same day, Finishes half an hour before it starts.
Please can someone help me with this?
10-17-2013 12:07 AM
The core of your issue is, I think, compatibility -- or rather non-compatibility -- of Outlook 2013...refer:
As with most things, trying to make two things work together that are incompatible typically is folly.
10-18-2013 09:55 PM
Nope...no idea. Given this is a user-to-user community, we don't have access to such "insider information".