I should have read the question more carefully. But, I just tried a
quick test and get different results. I just beamed an app from a IIIx
(PalmOS 3.3) to a VII. I then beamed some records. Then I beamed the
app again. I got an "accept" message box. I answered 'yes', but the
records are still there.
Is this deleting all DB's with the target creator ID a behavior of 3.0
that was later fixed?
Regards,
-jjf
-----Original Message-----
From: Danny Epstein [mailto:[EMAIL PROTECTED]]
Sent: Friday, March 31, 2000 4:26 PM
To: Palm Developer Forum
Subject: Re: Receiving app via Beaming
William F. Weiher III <[EMAIL PROTECTED]> wrote:
> Has anyone ever found a way to prevent the DB for an app from being
> deleted when a new copy is received via beaming?
"Fitzpatrick, Joe" <[EMAIL PROTECTED]> wrote:
> You can set the 'beam prevent' attribute on your PRC database.
Joe: I don't think you understood William's question. 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.
--
Danny Epstein
Palm
--
For information on using the Palm Developer Forums, or to unsubscribe,
please see http://www.palm.com/devzone/mailinglists.html
--
For information on using the Palm Developer Forums, or to unsubscribe, please see
http://www.palm.com/devzone/mailinglists.html
