Viren, >our palm-reader ( in-house >developed utility ) was going for a toss sicne it was assuming that >what would follow after 78 bytes would be really a record header ( b- >bytes)...however, things used to fall apart thanks to AppForge >implementations.
No, things fell apart because you made the assumption the recordlist info would follow a 78 byte header. Per the Palm OS docs you need to account for the AppInfoBlock, if present, and the SortInfoBlock, if present. It is not AppForge's fault if you made false assumptions. Doug -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
