[missing-sync-palmos-talk] Using conduits simultaneously that potentially could sync the same data

[Rob and Satoko at BECS]

Me too!!! (Just to lend my voice once again in support of this issue.) I've
been doing this with the Entourage and Palm conduits for a couple years now
with no data loss. In addition to making things clear to users, Perhaps you
could register known conduits, like the monolithic Entourage conduit, and
only allow those conduits to bypass the restriction against duplicate
function. Surely there aren't many of those, nor many new ones that come
along, and users will let you know when a new one comes along. This might
give you a little more secure feeling that your users weren't getting
themselves in trouble! Meanwhile, I'd also appreciate knowing about any
workaround, off list if you prefer, so I too can start enjoying my paid up
v4.

Thanks,

Rob

-- 
Rob Boyles and Satoko Fukushima
BECS
Matsuoka 1193-22
Fuji-shi Shizuoka 416-0909 JAPAN
TEL/FAX 0545-64-9650   +81-545-64-9650
becs at shizuokanet.ne.jp
http://www.becs.jp

> W Yu and Scott Gruby wrote:
> 
> . . . is the advanced option to bypass MS's internal
> check for
> duplicate conduit functions in the horizon?
>
> We have discussed this feature, but have not created a user interface
> to turn it on. We will look at adding it for a future version. Despite
> what some users say, there is a strong potential for data loss, so we
> need to make sure that it is clear to users before turning on the
> feature.
> 
> Yes, I couldn't agree more with your cautious approach. The day that feature
> comes out is the day I can practically migrate across to my paid up v4, and
> I suspect I am not the only one to benefit. Although a hack work around tip
> would be most welcome at this stage.  ;)