Mitch,
Method two should be fine. But you have to code for it.
If the preferences structure has not changed since the last release then
simply do not change the version number of the preferences get/set.
If it has changed then you need to put a little extra code in to get the
old version and then set the new version. If you place all the new version
data at the end of the structure you should be able to get the old version
using the new version structure (and the old version size) and then
initialize the new fields and set the new version preferences (with the new
size)
I am away from my code right now so I forget the exact lines I wrote but I
think you can get the jist...
Ron Gouldner
----------------------------------------------------------
RGPS Development
Makers of Quality Palm Computing Platform Software
PokerLogic, MindMeld, PilotEyes, PalmVHack and StayOffHack
http://www.rgps.com
[EMAIL PROTECTED]
----------------------------------------------------------
<pre>
I'm a little confused about the best way to distribute an upgrade to an app
I've written that uses RegCode as it's registration method.
Method 1) I could tell the users to completely remove my app from their
Palm
and then install the new version, go to the register screen and reenter
their unlock code.
Method 2) I could tell the users to just overwrite the old version of my
app
with the new version without deleting the old one first. This is the way I
would prefer to do it since it's fewer steps for the user and might
eliminate them having to contact me to find out what their unlock code is.
It assumes that the new version would see the prefs record from the old
version so it could see the unlock code.
My question is, is there any reason why I should not do it the second way?
Will overwriting the old version with the new version in any way mess up
the
new version's ability to see the old prefs data?
</pre>
