>This is fine, but this adds the appointment AT THE END of the database
>(dmMaxRecordIndex). However entries in the DateBook are stored in order
>(at least for non-repeating events; repeating events are different), so
>this means that the event will not be in order....
>So unless I'm missing something, adding
>something to the DateBook in this manner (that is, without determining
>where in the database it should be inserted) is very dangerous.
Steve:
Thanks for the warning. As it turns out, this finally reared it's
ugly head and bit me in the butt. My method did work fine, 19 out of
20 times. The side effect wasn't horrific, just an error and a soft
reset. But that's one problem I'd rather not have.
It sure pays to read the source code carefully, not quickly.
Regards,
Steve Mann
--
-------------------------------------------
Creative Digital Publishing Inc.
1315 Palm Street, San Luis Obispo, CA 93401-3117
-------------------------------------------
805.784.9461 805.784.9462 (fax)
[EMAIL PROTECTED] http://www.cdpubs.com
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
