5

I have one file in my filestructure (a FireBird database) that, once it is installed the first time, should never be overwritten again. This seems like an easy enough task, but I've wasted an inordinate amount of time trying fruitlessly to find an answer.

If you right click on the file and select "Properties", there is only an "Always Overwrite" checkbox. I would simply keep the version number the same, which I'm told would prevent a file from being overwritten, but that could be dangerous in my situation, and in the actual file properties, tere is no place to even be able to put a version number.

I had assumed this would be have fairly straightforward solution, but I certainly haven't found one yet.

Thank you in advance for any help, guys. You rock.

Cyprus106
  • 5,722
  • 6
  • 40
  • 48

1 Answers1

6

Two approaches:

1) The "easiest" way for InstallShield to never overwrite a file is for it to never install it in the first place. Install it as a.txt and have your application copy it to b.txt on first run and I nstallShield will never even know about b.txt in the first place.

2) Create a component in InstallShield and add your database as the keyfile. Presumably the contents of the database will change over time and result in a creation date and modification date that are different. In this scenario, InstallShield's ( Windows Installer actually ) default file versioning rules ( OMUS ) dictate that the file will not be overwritten.

3) If #2 is still not working somehow then set the Never Overwrite attribute on the component to Yes.

Remember, file costing is based on the KeyFile. Whatever the keyfile evaulates to, all the other files in the component will do the same thing with regard to overwrite. "Always Overwrite" is "version lying" where we falsely tell MSI that the file Verison is 65535.0.0.0 and thus the Create / Modification rule is superseded by the Versioned trumps Non-Versioned files rule.

Christopher Painter
  • 54,556
  • 6
  • 63
  • 100