I have one final question for this thread. As has been mentioned previously (and mentioned in the Rhodes and McKeehan text), the record header actually only uses 3 bytes to store the unique ID. However, there is information regarding this in the Palm OS Reference, at least that I could find. The prototype for DmSetRecordInfo takes a pointer to a UInt32 (4 bytes) for this paramter:
Err DmSetRecordInfo (DmOpenRef dbP, UInt16 index, UInt16 *attrP, UInt32 *uniqueIDP) So, how would one go about actually making a call using DmSetRecordIndfo to replace the system generated unique ID with a custom one? If I simply make sure that my custom unique IDs are less than 16777216 (3 bytes), is it OK to simply pass in a pointer to a UInt32 holding the unique ID? Or is there something else that I need to do? Once again, I am very appreciative of everyone's help. -Sean In article <93902@palm-dev-forum>, Matt Hebley <[EMAIL PROTECTED]> wrote: [snipped: discussion about storing custom record unique IDs in the record header] > > > > Could you elaborate on storing them in the hearder? I am not sure I > > understand how I would go about doing this. > > > > -Sean > > Look at DmRecordInfo and DmSetRecordInfo. > > Matt -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
