If a file is being copied from one local directory to another one during a Folder Compare session, the new file will have its archive attribute set, irrespective of whether the archive attribute was set on the original file.
If the file is being copied from an FTP server instead, the archive attribute will not be set on the local file, which is a bit irritating.
Beyond Compare 2 was more consistent in that files that were created in a Folder Compare session always got their archive attribute set, irrespective of their origin.
Is there a configuration setting to change the behaviour of BC3 ?
Thanks,
Henning
If the file is being copied from an FTP server instead, the archive attribute will not be set on the local file, which is a bit irritating.
Beyond Compare 2 was more consistent in that files that were created in a Folder Compare session always got their archive attribute set, irrespective of their origin.
Is there a configuration setting to change the behaviour of BC3 ?
Thanks,
Henning
Comment