PylonPro

EasySync virker - med lidt held :o) Bruger det dagligt.

Køb den på www.lotus.com

/Rob

EasySync kører, som Hobbez siger, godt.
Jeg selv vil dog anbefale Pumatech\'s Intellisync. Særdeles konfigurerbar, og meget stabil. Om du vælger den ene eller den anden er vist en smagssag :-)

Programmet kan hentes i en trial, og efterfølgende købes på http://www.pumatech.com/products.html

NanoQ

Jeg har EasySync kørende som et ikon i min bundlinje og bruger det ved hver synkronisering, men problemet opstår når jeg skal synkroniserer med min hjemme Pc, så laver den dobbelt bookning og når jeg så kommer på job og synkroniserer så er det rigtigt sjovt (mange aftaler i kalenderen)

Det er netop ved syncronisering til flere pc\'er jeg er mægtig glad for Intellisync. Jeg har dog ikke prøvet Easysync i den forbindelse.

NanoQ

Mister >> Hmm, kører du Notes både hjemme og på jobbet?

Det virker som om du bruger både Easysync og PylonPro - det ene system det ene sted, og det andet system det andet???

I relation til dubletterne, så tag et kig på http://www.palmgear.com/software/showsoftware.cfm?sid=41290020010207042946&prodID=756

/Rob

Nej jeg nruger kun Easysync og får så dubletter

OKKO, fra Lotus websted:

Problem:

Can Lotus EasySync be used to synchronize multiple files (for example, multiple OR4 files) to one 3COM PalmPilot/IBM WorkPad?

If so, what can you do to prevent duplicate entries?

Solution:

EasySync is designed to synchronize on a one-to-one ratio; one file to one Personal Digital Assistant (PDA). However, there are ways to prevent duplicate entries when synching to more than one file.

One cause of duplicate entries is an incorrect match of the entry ID in the file and the PDA. Each entry on the PDA is assigned an internal ID. When the entry is synched to either a Notes database or an .OR4 file, the internal ID is transferred along with the entry to the storage file. When the PDA is taken to another computer with a different storage file and synchronized, all of the internal entry IDs on the PDA are changed because each data file has its own ID generator.

For example, the entry, Test, on the PDA has an ID of 1234. When synched to File_1, the ID remains the same: 1234. However, if the PDA is taken to another machine and synched to File_2, the ID is now changed to ABCD. One reason for the change of ID is a conflict of the internal entry ID.

Once the internal IDs on the PDA are changed and the PDA is taken back and forth between files and systems, duplicate entries will occur. Even though the entries are the same in terms of description and data, the IDs are different and EasySync will interpret the incorrect match up as two different entries.

One way to resolve the duplicate entries (although not 100% reliable) is to change the action of the particular conduit to \"PalmPilot Overwrites Desktop\" or \"Desktop Overwrites PalmPilot\". Doing so will make one of the storage files (PDA or .NSF/.OR4) the master of the data. In the event of duplicate entries, what the action specifies will be the one to keep.

Supporting Information:


/Rob