> My application requires a unique id for each record. The item "uniqueID" in > the record list seems ok for my purpose. However I need to confirm that the > uniqueID is really unique.
It's not 100% guaranteed, but for all practical purposes, it's unique. The database has a seed which is incremented each time a record is created. If the device is hard reset and the data is restored from the desktop, a new random seed is chosen. It is possible, but unlikely, that this new seed will have been used before. The more times your hard reset and restore, the more likely it is that an ID conflict will occur. > For example, if I delete one record, I need to be sure that the uniqueID > associated with the deleted record won't be used in future by other newly > added record! If that happens, I cannot use the built-in uniqueID. I will > have to somehow keep track of my own. You can use your own ID within each record if you want more control. Finding a record by built-in ID is a fast linear operation. If you sort your database by your own ID, finding a record will be a slow O(log n) operation. Which is faster depends on the size of the database. -- Danny @ Palm -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
