Hi, a customer of mine has reported a problem he's having: he accidentally preinstalled and distributed on _some_ palms a development version of an application, never meant for public distribution. On some other palms he distributed the correct, final, version. The former interim version used to save its data with some field values inverted with respect to the final version (but the db version number and format is *exactly* the same, so there is no way to distinguish the version by looking at the db). Now he wants to redistribute an upgrade version, converting the old db's to the new data layout on the palms with the "wrong" application, and simply doing nothing (db-wise) on the other ones. Since he'd like to avoid putting burden on final users, his preferred solution would be to craft an upgrade application with the same name and creator id, discerning the db format by looking at some peculiar characteristics of the previously installed binary (size, creation time, ...). I was thinking about bumping the version number of the new application to a higher value, keeping the same name and creator ID, and using DmGetNextDatabaseByTypeCreator() to get to the "older" app. Is it feasible? In other words, does the HotSync process maintain the previous application with a lower version number, or is it automatically removed? Do you envision a better strategy to solve this problem?
Thanks in advance, Marco -- ======================================================================== Marco Pantaleoni [EMAIL PROTECTED] Padova, Italy [EMAIL PROTECTED] elastiC language developer http://www.elasticworld.org -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
