[missing-sync-palmos-talk] Re: missing-sync-palmos-talk Digest, Vol 17, Issue 13

[Ken Freeman]

The 4.0.1 version does have an option to allow conflicting conduits.
HOWEVER, enabling conduit conflicts could cause data corruption! You will
get a warning dialog explaining that Mark/Space does NOT support or take any
responsibility for activating and using this mode.

1) Launch Missing Sync and type Command-Option-Shift-d.
2) Check the option "Allow conduit conflicts"
3) Click OK.

Missing Sync will no longer warn you, or prevent conduit conflicts. This
does allow you to mix conduits like setting Entourage to handle memos and
another PIM for Date Book. That situation is not as likely to cause
problems. The real problem, which has NOT been fully tested, and again
Mark/Space does NOT support or take responsibility for any results, is if
you assign two conduits to sync the same database type (e.g. Both Entourage
and iSync/iCal to sync with Date Book).

Ken


On 10/14/04 4:34 PM, "W Yu" <mail at wlinkw.com> wrote:

> I am in a similar bind but my conflicting conduit under MissingSync's eyes
> are Entourage and Now-Up-to-Date.
> 
> My specific preference is to track Memos in Entourage but diary and to-do
> entries in Now-Up-to-Date for its support of DateBk5 categories. The
> solution of creating another profile from a user's point of view is still a
> "pain". I'd think there should at least be an optional setting within
> MissingSync to allow advanced users to bypass the internal checking process.
> 
> Cheers!