Baxter, >You may be right. Has some interesting implications, however, for utilities >such as Par and PDB Reader and even the Emulators and Simulators - which are >apparently failing to correctly analyze the pdb file.
That isn't really true. Palm OS does not enforce the "uniqueness" of the unique ID. So getting a pdb on the system via some other method whether VFS file copy, IR beaming, emulator / simulator drag N drop, or whatever is not a matter of failing to analyze the file. They simply have no reason to care about the "unique" IDs. Conduits care because their purpose is to synchronize records, and the unique ID is the proper way to identify the data instead of using data itself. For example, in the Address / Contacts database, you can correct the spelling of a name or phone number, or completely change a name (e.g. someone gets married) on either the device or the desktop, and on the next sync it will still recognize which record should be updated even if you have changed virtually every field. When you create a PDB yourself, you should either not care about the unique ID value -- in which case you should leave it zero and let one be assigned for you -- or you should provide a unique value. When you provide a non-zero value, Hot Sync does what a conduit should -- uses it to identify the record. But other than synchronization, there is no real value to the unique ID so in my view it isn't a matter of other utilities failing to correctly analyze the pdb file. Doug -- For information on using the PalmSource Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
