Just so you know... the palm database file format

Trivial, I know, but some people need to know these things.
From the start we have the header, appinfo (optional), sortinfo (optional) followed by the record entry headers.
The header is:

Field	Size	Value
Db Name	32	Ascii Database Name
attributes	2	See DataMgr.h for meaning (dmHdrAttrResDB)
version	2	Version number an application would use this to decide if the content was compatible
creationDate	4	Creation date of the database - time from the palm epoch when it was created
modificationDate	4	Last modifiied date of the db. creationDate by default.
lastBackupDate	4	date last backed up ina hotsync
modificationNumber	4	when changed this gets bumped
appInfoID	4	Offset in this DB to the appinfo block (0 if it does not exist).
sortInfoId	4	Offset in the DB to the sortinfo block (0 if it does not exist)
type	4	the 4 character type of the pdb
creator	4	the 4 character creator of the pdb
uniqueIDSeed	4	Stumped - I don't know what this is for, leave it at 0
This is the end of the header structure, the next is the record entry information

Record list:

Field	Size	Value
nextrecordList	4	Address of the next record list (only used for really bit pdbs)
nRecords	2	Number of records in the recordlist
pad	2	Number of records in the recordlist
nRecords items	4 * nRecords	Addresses of the records in the pdb

The address of the first record usually lies immediately following the appinfo and sortinfo data. As this data is consumer defined, the only way of determining it's size is to use relative calculations. For example, the size of the appinfo structure it's local address up to min(addr(sortinfo, Address of any data records)) - 1. The size of the sortinfo structure is it's local address up to the min(Address of any data records) - 1. They are application defined, and as such should not be messed with.