>>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.
It is much safer to use the exchange manager if you're just trying to
insert a record into one of the PIM apps. Turn on loopback mode, turn off
the "prompt to recieve" option, and you're done, and it'll even not break
when we change the PIM record formats. Decreases your code size, increases
safety, such a bargain. Does require 3.0 or higher, but that usually is
fine.
-David Fedor
Palm Developer Support
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palmos.com/dev/tech/support/forums/
