I remember hitting this same bug a couple of years ago. Annoying one isn't it? When the Launcher asks the user whether it's okay to replace the existing app, and the user says "yeah, go ahead", the Launcher was deleting not just the app, but all associated databases as well. This means a user who upgrades by accepting a new version beamed from someone else's device ends up losing all their data. Not good.
Work-arounds exist, but they have their problems. For example, you could give the new version of your app a new creator. That would let it coexist on a device with the old version, and it would mean the user would have to delete the old version. They might delete the old version before running the new one. So, to be sure you transfer their data in time, you'd catch both the reset and sync notify launch codes, and check for old data at that time, moving the data into a database with the new creator. You could go a step further and automatically delete the old version of the app. Or you could document the problem and hope it doesn't catch too many users off guard. -- Peter Epstein -- For information on using the Palm Developer Forums, or to unsubscribe, please see http://www.palmos.com/dev/support/forums/
