At 10:18 AM +0200 12/13/99, Mick Doe wrote:
>I am making an application which uses the Palm OS's unique IDs as
>references. I am not going to have a conduit - just backup my DB during the
>hotsync. So the problem you described above does consider to my app?
>
>Do I need to use my own unique IDs in this case?
The amazingly informative knowledge base article
http://oasis.palm.com/devzone/knowledgebasearticle.cfm?article_id=1085 says:
>Palm Computing's built-in Backup/Restore and PIM conduits change the unique IDs of
>records during a full restore by versions 1.x of Windows and Macintosh HotSync
>Manager. While
>this can clear up unique ID range fragmentation, it breaks links and multi-desktop
>synchronizations. Windows HotSync Manager versions 2.1 and later don't change the
>unique IDs of records on devices running Palm OS 2.0 and greater. All versions of
>HotSync Manager change the unique ID of restored records on Palm OS 1.x devices.
The only remaining question is what more recent versions of Macintosh HotSync Manager
do.
So the answer to your questions depends on which version of Palm OS and HotSync
Manager you want to support. I wouldn't worry about Palm OS 1.x since there are hardly
any devices left running it. OTOH if HotSync Manager 2.1 for Macintosh doesn't
preserve unique IDs, I'd be concerned. Perhaps the knowledge base article should be
updated to indicate whether it does?
-
Danny Epstein, Applied Thought Corporation
Have friends with Palm organizers? Get BeamBooks!
http://www.appliedthought.com/beambooks
