A trick that I use is to put a version number in the preferences for the application. This gives you a lot more flexibility to do neat stuff like update record layouts in databases, add new fields to the preference structure, and the like when you release an upgrade for an application.
The down sides is you will have to support all of these upgrade routines for a fairly long time. You'll also have to consider those who jump up multiple versions (the customer is upgrading from version 1 to version 5). This also introduces some useless code (run at most once) if you put the upgrade support in the application (although you might be able to put the upgrade logic in a shared library that could go away after it has executed). And you really have to make sure that the upgrade is fool-proof - nothing worse then deleting some important data on a user due to a programming error or an "unforeseen circumstance" (you remove a field from a recod in your app that the customer happened to use to keep track of his kids' birthdays, for example). At 12:00 AM 6/3/2002 -0700, Ben Combee <[EMAIL PROTECTED]> wrote: >In article <87859@palm-dev-forum>, [EMAIL PROTECTED] says... > > > > Hi, I have a few questions, hope someone will tell me what I want to > > hear ;-) > > > - Does a boolean flag exist to know if the palm file&apps db has changed > > since > > last consultation ? > >No. > > > - Does a global value exist with the number of apps&files ? > >No. > > > - Does a vector exists with all the apps and files listed ? > >Not always, but it can be created using the SysCreateDataBaseList API. ---- Tom Frauenhofer, [EMAIL PROTECTED] http://www.beret.com "Playing harp takes lots of pluck, a love of music, and a pick-up truck." - Valentine Frauenhofer -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
