You have two options. 1. You can use DatebookDB.c/.h to create records in Datebook's database that are in the same format as the existing records. The danger is that Datebook will change the format it uses for its data, something we've said won't happen in Palm OS 5, but will happen in the next big release after that.
2. You can use the Exchange Manager to do a local send of a vCalendar object to Datebook (or whoever registered for text/vCalendar and/or .vcf). This is done using the localMode flag in ExgSocketType. On Palm OS 4.0 and later, this invokes the local exchange library. Prior to that, this causes the IrOBEX exchange library to "loopback" rather than beaming. You don't have to hard-code Datebook's database format into your app this way. The downside is that you have less control over the UI. You may have trouble avoiding progress and "do you wanna accept" dialogs on some versions of Palm OS. Someone just reported a bug using the Exchange Manager approach: http://www.escribe.com/computing/pcpqa/m58373.html I haven't looked into this yet. Here's a similar question from the archives: http://www.escribe.com/computing/pcpqa/m25090.html Follow the thread links to see the answers. - Danny -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
