Steve, either you or I misunderstood the original question
(or I misunderstood your response).
>From what I interpreted, the problem is that when you have
an app v1 on your Palm, and somebody beams you app v2,
the Palm will delete app v1 (and thus all of it's associated
databases & preferences) before it accepts app v2. When
you hotsync this does not happen but when you beam an
appl, you're toasting the old one first.
I don't know if there is anything that can be done about
this, since it's the OS handling of DBs of type appl received
over the IR.
--
-Richad M. Hartman
[EMAIL PROTECTED]
186,000 mi/sec: not just a good idea, it's the LAW!
Steve Sabram wrote in message <6772@palm-dev-forum>...
>
>You could have a utility in you app that works with this DB to rename the
old one before the new one is beamed in. Also, if this
>is a DB that is continually being updated by you the publisher, you could
put the date in the DB name such as
>"Yours31Mar2000DB.pdb". Your app can then search databases of that creator
and filetype to build a list that is selected by the
>app or the user.
>
>Steve
>
>"William F. Weiher III" 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? If there were a way for the app
to
>> know it was being replaced, I could do something about protecting the DB
but
>> I wouldn't want to do that whenever the app is not running (you might
really
>> want to delete it with delete from the app menu)
>>
>> --
>> 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
