For the most part, new versions should install directly over the old one
without a hitch.  But I've had a similar problem when I used a different
output name in the Project Settings | PalmRez Post Linker.  Switching the name
back fixed the problem, but now I'm stuck with the same name for the life of
the app.

I'm guessing you did something similar, such as "MyApp" becoming
"MyAppGerman"?

--Mike Y.


-----Original Message-----
From: Christian Vandendorpe <[EMAIL PROTECTED]>
To: [EMAIL PROTECTED] <[EMAIL PROTECTED]>
Date: Monday, January 17, 2000 10:24 AM
Subject: How prcs get installed


Hi all,



I'm wondering how the Palm decides to install a prc and when an existing prc
will be overwritten with a new prc.



I have this strange situation where I have 2 prc's with different filenames
(ie MyPrcA.prc and MyPrcB.prc) but they have:



- The same version number in Constructor

- The same application name in Constructor

- The same version number in the CodeWarrior project settings

- The same application ID in the CodeWarrior project settings



but when I install one over the other, if I then go into
Applications->Info->Size the size shown is not 60K (the size of my app) but
120K. So somehow instead of MyPrcB.prc replacing MyPrcA.prc it was aggregated.
Also launching the program actually run MyPrcA.prc.



This is quite annoying because I just released a German version of my app and
there was no way to make it replace an existing English version. I had to
write complex installation instructions instructing users to delete the
existing app, install the new one and then recover their database from their
backup directory.



Can anybody offer a solution? I thought that the physical filenames had no
effect on Palm programs!



Thanks a bunch



Chris





This message sent using EMUmail.  http://EmuMail.com


  • Ho... Christian Vandendorpe
    • ... Michael Yam
    • ... Christian Vandendorpe
    • ... David Fedor
    • ... Созин Борис
    • ... Scott Maxwell
    • ... Scott Maxwell
    • ... David Fedor
    • ... Richard Hartman

Reply via email to