"Install File" action ignores "Never Overwrite"

[DanCooperstock]

I put an action into my After Install actions that did an Install File, copying one already-installed file to a 2nd filename, with the "Never Overwrite" option selection. When I ran it, it did overwrite an existing file by that name!

The Copy File does not seem to have this (apparent) bug, if you select it's checkbox to not overwrite.

Any comments?

[Darryl]

Re: "Install File" action ignores "Never Overwrite"

In a test of mine, I wasn't able to replicate any problem with the file being overwritten through an Install File action. Can you replicate the problem in a new project file with only that one action? Perhaps there is another cause?

What OS are you testing on?
What build of the product are you using?

I would like to replicate it on my end.

[DanCooperstock]

Re: "Install File" action ignores "Never Overwrite"

I can definitely replicate this in a tiny install. I don't know how to attach anything to this post, so you can download my setup file from http://www.FreeDonationSoftware.org/...nstallFile.sf6

To test, create two different files, "c:\Program Files\Donation\Data\donation3.empty", and "c:\Program Files\Donation\Data\donation3.db". The action is to Install the .empty file to the .db file, but it's set to never overwrite. But it does overwrite.

I'm on Windows 2000, using SF 6.0.1.2, Evaluation Version.

[Darryl]

Re: "Install File" action ignores "Never Overwrite"

Hi,

Thank you very much for providing the extra information. I've submitted a report for our developers to look into. Currently in the documenation, the "If file already exists" options only apply if that file is the same name, so your example should not work by design.

However I also tested with a file of the same name and yes, the setting does not have any effect currently.

However if you specified just a folder as the destination, the options seem to work fine, which is what I orginally tested.

I'm not sure at this point whether this is a documentation error or a functionality error, so the developers will make that decision when looking into the issue. Thank you for pointing this information out.