On Tue, Jul 16, 2002 at 01:39:10PM -0700, Danny Epstein wrote: > > 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. > > The Install conduit will overwrite the existing database in this situation. > If you don't want it to do this, give your new database a different database > name. The creator IDs can still be the same. Your new version can look for > the old version on sysAppLaunchCmdSyncNotify. If it finds it, it can delete > it and correct the data format. You might want to delay this action using an > alarm to avoid potential problems with modifying a collection being > enumerated. Your app can change its own database name after being installed > if you want to end up with the same database name. The user doesn't see the > database name anywhere, so it doesn't really matter. Again, I'd delay this > change with an alarm.
This seems to be the solution I was searching. Thanks. By the way, if I understand correctly, an alarm is always triggered _after_ a system operation, like a HotSync, so that I can just pass TimGetSeconds() as the fourth parameter to AlmSetAlarm(), right? Thanks a lot! 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/
