> One example is easy to reproduce: Pass 0xFFFFFFFF to the uniqueID. It will > give out fatal says" DataMgr.c, line 6184, invalid uniqueID passwd"
That makes sense since unique IDs are 24-bit values. > Can someone from PalmOS tell me that the fatal only happens when the uniqueID I > passed blows the 3 byte bounds? There are other cases where it puts up an alert, but they're things that should never happen. For example, after it finishes iterating through all the records without finding the ID it's searching for, it verifies that the number of records it iterated over is equal to the number of records specified in the database header. This is just asserting an invariant. Looking at the source code, I can't find any "normal" cases where DmFindRecordByID puts up an alert. It sounds like you haven't found any in practice either. In that case, the bug's in the docs. Thanks for reporting this; we'll get it fixed. - Danny @ Palm -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/tech/support/forums/
