[missing-sync-winmobile-talk] Re: MSWM 2.0.2b2 (BETA) & Entourage
Ken Freeman
kfreeman at markspace.com
Tue Sep 13 15:21:01 PDT 2005
On 9/13/05 2:39 PM, "s.strippoli" <sstrippoli at mac.com> wrote:
>
> On Friday, September 09, 2005, at 1:01PM, <kfreeman at markspace.com> wrote:
>
>> Thanks to Sabino for sending his data so we could see this problem in house.
>> The issue he reports is due to a unique limitation on the device.
>>
>> The "AACPS Leadership Conf" event can not be moved to the device because the
>> event is a daily event (for two days) and the alarm is 2 days before. So the
>> alarm for the 2nd instance occurs before the 1st instance ends. The device
>> does not like that type of event.
>
>> If you try to create this on the device you will get the following
>> error dialog:
>> "Cannot save. Select a reminder time that occurs after
>> the previous occurrence ends."
>>
>> So since the device itself cannot handle this event type, an error is logged
>> during the sync. In the next beta build, the following will now be written
>> to the log:
>
>> Device Communication: ERROR: Couldn't send "AACPS Leadership Conf" to
>> device. Alarm time must occur after the previous occurrence ends.
>
>> So the user must edit the event to enable it to sync to the handheld. The
>> device will not allow a two day advance reminder for this type of event.
>
> DEAR KEN -
>
> THANK YOU FOR ACKNOWLEDGING MY SUPPORT POSTING.
> I WAS PREVIOUSLY UNAWARE OF THIS LIMITATION (is limitation of device or of
> WinMo 2003 ?)
This is an example of a device limitation.
> (likely because most of my entries are made in Entourage on the computer)
> SO I TRIED TO CREATE THIS SAME TYPE OF EVENT "2-DAY RECURRING w/ALARM"
> ON THE SAMSUNG i730 DEVICE (WinMo 2003) TO REPRODUCE & SEE THE ERROR MYSELF.
>
> HOWEVER, I *WAS* ABLE TO CREATE AN 30 MINUTE-EVENT-WITH-AN-ALARM WHICH
> OCCURS TODAY AND RE-OCCURS TOMORROW. THE EVENT APPEARED CORRECTLY ON
> THE HANDHELD'S CALENDAR AND THE ALARM FOR THE FIRST EVENT (Today's)
> SOUNDED. !?
>
> WHAT AM I MISSING OR NOT UNDERSTANDING ?
I agree that this is confusing. Let me give an example to explain. You can
easily create a recurring daily event, for example that happens today and
then tomorrow. You can also add an alarm to that event. But, if that alarm
settings would cause the second alarm to occur before the previous event,
the DEVICE can't do that.
So you can create a daily repeating event that starts today at 5:00pm until
5:30pm and set the recurrence to end tomorrow (there's our two day event).
If you leave the default alarm setting to 15 minutes before, the event is
accepted by the device.
But, if you edit that same event and change the alarm popup from 15 minutes
to 15 days (or in this case even 1 day), and then tap the OK button to
accept that change, the device will alert you that "Cannot Save. Select a
reminder time that occurs after the previous occurrence ends. In this
example the maximum alarm would be 23 hours or even 1439 minutes (1 less
minute than 24 hours).
In your original "AACPS Leadership Conf" event you set the reminder for 2
days. You want to be reminded 2 days before the event so you can prepare. A
very reasonable thing to want to do. But, since this was a recurring event.
The second occurrence alarm would occur before the previous occurrence even
ended, and the device doesn't allow that.
Entourage and iCal do allow that, so when we sync we have to alert you of
this in the log and we cannot sync that record. We log the error, skip the
record and keep syncing everything else.
>
>
>> While this event was not so strange to Mr. Strippoli, it is one more example
>> of unique complex data event that does not sync. . . . . . ((add'l text
>> omitted))
>
>> Ken
>
> KEN,
> I DON'T THINK THIS TYPE OF EVENT IS THAT STRANGE OR UNIQUE AT ALL !!!
Correct. Your reason for an alarm two days before the event is not strange.
The fact that someone at Microsoft said, the device can't have an alarm for
a recurring event before the end of the previous occurrence is the strange
part.
My point is that this is a unique example of how complex the synchronization
of data from iCal to the device can be. It's more than just matching up the
fields and passing them back and forth, because of these types of device
side limitations and differences.
Ken
> I BELIEVE IT WOULD CREATE MORE PROBLEMS TRYING TO EDITED ONE INSTANCE IN
> A RECURRING SERIES (TRYING TO TURN THE 2ND ALARM OFF WHILE KEEPING THE
> FIRST).
> THINK I RECALL READING THAT CHANGING ONE INSTANCE IN A SERIES WILL RESULT IN
> THE LINK IN THE SERIES BEING LOST AFTER SYNCING. SO I WANTED TO AVOID
> THAT.
Yes, making a change to one instance can create what is called a "detached
event."
>
>
> sabino
>
>
> - - - - - - - - - - - - - - - - - - - - - - - - - - - - - - -
>
>> On 9/9/05 9:09 AM, "s.strippoli" <sstrippoli at mac.com> wrote:
>
>>> To Ray Towry, Will Blackie, other Entourage users and mark/space support -
>>> i was a bit hesitant that i might have become overly optimistic
>>> thinking that they have finally identified and addressed the primary issues
>>> interfering with smooth syncing of Entourage Calendar using MSWM v2.
>>>
>>> for what its worth, i finally made time, downloadED new beta TO try it out.
>>> YES, it did advance ... longer/further into a complete sync of Calendar.
>>> However, ... it still did NOT complete successfully :-<
>>>
>>> this was with trashing prefs & prior data files on Powerbook (OSX 10.3.9)
>>> then totally deleting ALL Calendar events on handheld, and soft reboot.
>>> and tried sync of **just CALENDAR** with Entourage overwrites handheld.
>>> the resulting log entries were extremely brief or few (see below).
>>> the 1st Error MSWM gagged on was *recent* recurring event 6-21 to 6-22-2005
>>> (( 2 consecutive days, with a STOP date specified ))
>>> then wenton to choke twice on annual recurring event(birthday)WITH a Stop
>>> date.
>>>
>>> I AM GETTING WORN OUT.
>
>>> sabino strippoli
>>>
>>>
>>> COMPLETE LOG ENTRY
>>> 9/8/05 04:07:29 Listener: Device Connecting: name "S_mobile" class
>>> "PocketPC" hw "SAMSUNG SPH-i730"
>>> 9/8/05 04:07:30 Listener: owner "sabino's PDA" ip "192.168.206.206"
>>> 9/8/05 04:07:30 Listener: Moved partnership id: 1052379047
>>> 9/8/05 04:11:20 MSUI: Entourage: Error adding record to device. Error
>>> 2147745895. AACPS Leadership Conf 20050621T130000
>>> 9/8/05 04:11:20 MSUI: Entourage: Error adding record to device. Error 1.
>>> Error 32. Ino's Birthday 20010307T200000
>>> 9/8/05 04:11:20 MSUI: Entourage: Error adding record to device. Error 1.
>>> Error 32. Ino's Birthday 20010307T200000
>>>
>>>
>>> = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = = =
>>>
>>> On 9/6/05, 07:54PM, Ray Towry <rtowry at ephrata.org> replied:
>>>
>>>> Ken,
>>>> In reviewing the release notes of the new beta, I see no mention of
>>>> entourage fixes or am I missing something? (Particularly dealing with
>>>> recurring events that are set on the custom menu every third Wednesday of
>>>> the month.) That's my issue.
>>>>
>>>> Any idea on when we can expect a fix for these and other entourage fixes I
>>>> haven't run into yet, or is there another problem that this release fixes
>>>> that will allow this type of synchronization (the hip bone's connected to
>>>> the leg bone type of thing).
>>>>
>>>> Will downloading it help me any with these issues?
>>>> Thanks,
>>>> Ray
>>>
>>>
>>>
>>>
>>> On 9/6/05 3:26 PM, "Ken Freeman" <kfreeman at markspace.com> wrote:
>>>
>>>>> A new BETA version of The Missing Sync for Windows Mobile, version 2.0.2b2
>>>>> is available for download at www.markspace.com/testing. This beta is
>>>>> recommended for those who have had problems synchronizing either Entourage
>>>>> data, iCal data or Address Book. You can install the 2.0.2b2 version right
>>>>> over the current 2.0.x version.
>>>>>
>>>>> The "Release Notes", viewable at www.markspace.com/testing, list problems
>>>>> fixed with this build, and the "Known Problems" link lists a few known
>>>>> problems and troubleshooting steps if you still get an error trying to
>>>>> sync
>>>>> with this build.
>>>>>
>>>>> We thank users for their patience and for sending us sample data files
>>>>> that
>>>>> enabled us to reproduce and fix specific data problems that prevented some
>>>>> users from being able to synchronize.
>>>>>
>>>
>>> _______________________________________________
>>> missing-sync-winmobile-talk mailing list
>>> missing-sync-winmobile-talk at lists.markspace.com
>>> Unsubcribing information, subscription options and list archives can be
>>> found
>>> at:
>>> http://lists.markspace.com/mailman/listinfo/missing-sync-winmobile-talk
>>
>>
>> _______________________________________________
>> missing-sync-winmobile-talk mailing list
>> missing-sync-winmobile-talk at lists.markspace.com
>> Unsubcribing information, subscription options and list archives can be found
>> at:
>> http://lists.markspace.com/mailman/listinfo/missing-sync-winmobile-talk
>>
>>
> _______________________________________________
> missing-sync-winmobile-talk mailing list
> missing-sync-winmobile-talk at lists.markspace.com
> Unsubcribing information, subscription options and list archives can be found
> at:
> http://lists.markspace.com/mailman/listinfo/missing-sync-winmobile-talk
More information about the missing-sync-winmobile-talk
mailing list