Danny Epstein wrote in message <6791@palm-dev-forum>...
...
> AFAIK there is no
>solution to William's problem. If you beam an app to someone who already
has
>the app (typically an older version of it), the old version will be deleted
>ALONG WITH ITS DATA. Obviously, we're aware of this problem.
>
>The only work-around I can think of is really ugly. You assign a new
creator
>ID for each version of your app. You make your app search for old data and
>automatically convert it to the new format. This could be as simple as
>changing the creator ID of the database, but it could involve arbitrary
>format changes as well. This work-around doesn't help if an app is
>overwritten with the same version, but this is probably much less common.
>
>This isn't an official Palm recommendation; it's just an idea that might
>work. I haven't even tried it.
>
Here's another work-around, but it's manual not automated.
Before accepting v2 of an app, the person who has v1 should use
one of the db utilities like ZarfCatalog to delete the v1 app. ZarfCatalog
has an option to delete -only- the appl without deleting the associated
data files & preferences.
Until Palm fixes the OS behavior on accepting appl databases,
this is the only workaround I can think of.
--
-Richard M. Hartman
[EMAIL PROTECTED]
186,000 mi/sec: not just a good idea, it's the LAW!
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
