Not at all. But do you know a better format than vCal/vCard to be independant of the db structure, the plateform, ... ?
For instance you cannot get records as vObject, so you have to access the db directly to read a record. But if your application only needs to save data in the db, the better solution is to use vObject and not (in this case) access the db directly. Ludovic Stringer wrote: > At one point PalmSource were saying they'd provide an API to > access the DB of the PIM's, and that API would allow the underlying > DB formats to change without breaking the many programs that > access the PIM DB's. Until the API is provided, you'd have to > access the PIM DB directly. > > Is this statement from Ludovic a retrenchment from that position? > > Roger Stringer > Marietta Systems, Inc. > > >>Subject: Re: Datebook questions >>From: Ludovic Ferrandis <[EMAIL PROTECTED]> >> >>This is not the good solution. It's a working solution, but definitevely >>not the good one. The main reason is that the struct db could change and >>your program won't work anymore. >> >>------------------------------ >>Steven M. Jerrett wrote: >> >>>The structure of the database is described in DateDB.c. >>>When dealing with the native Palm apps and the structures they use, I >>>have found it best to study the actual code for those applications. The >>>source code for the Datebook applicaton is fairly well documented. >>>------------------------------ >>>[EMAIL PROTECTED] wrote: >>> >>> >>>>I have to make a program which can put a new record in the datebook as >>>>we are in the datebook program. Then I would like to know how it is >>>>possible to insert a new record in the datebook database when I am in >>>>my application, I have open the datebook source code but I don't >>>>understand how is the database. >>> > > > -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
