VV 3.0 - Move files - How are conflicts handled in Destin'..

Alice · Joined: 29 Jan 2015 Posts: 262

Hey there.

Taking a closer look at the Move function in ViceVersa Pro 3.0 - Build 3002 - (64-bit). What happens when a conflict occurs as the moved file arrives at the Destination and meets an existing file ?

does VV :

- rename the Destination file
- replace the Destination file
- skip

Could a future build allow one of the three behaviours to be selected and be 'in effect' for a given Profile please ?

TGRMN Software · Site Admin Joined: 10 Jan 2005 Posts: 8684

Hi, what is it meant by conflict? A newer file in target? thanks
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

Alice · Joined: 29 Jan 2015 Posts: 262

Hello, sorry for not being clear.

In my scenario the Destination file(s) would always be older than the Source. So VV would overwrite the Destination file in the current build when using a Move operation, but it might be handy to 'skip'/'rename' where files already exist in the Destination

TGRMN Software · Site Admin Joined: 10 Jan 2005 Posts: 8684

Hi, like move but only if there is no file with same name and location already in target (do not overwrite existing files)
_________________
--
TGRMN Software Support
http://www.tgrmn.com
http://www.compareandmerge.com

Alice · Joined: 29 Jan 2015 Posts: 262

I guess I'm proposing two new 'switches'.

'if matching file present in Destination' :

1) Rename it
or
2) Skip it

that could apply for other VV 'Methods' eg Backup (Mirror Source to Target) too, or maybe you could consider creating a new 'Method' to allow 'Renames/skips', just an idea