..whereas the Help File says.. "A file is defined as different if either its timestamp or size has changed."
The tooltip behaviour (more recent timestamp) is what I expected but the latter behaviour (changed timestamp or size) seems to be the case here.
The timestamp of the source file is older than the target so it would appear that SIZE difference trumps TIMESTAMP if both are different. This seems like a dangerous default to me.
The internal COPYEXISTING command has the option Copy UPDATEEXISTING=date to ignore size difference, but the COPYUPDATE command does not appear to have a way of applying the same safety net.
[quote="Nobmen"]10.0.5.0
on desktop ok
on network the same behavior[/quote]
On 10.0.5.0 I still see the problem with Copy UPDATEALL between two local drives.
If destination file has different size, it implicates that the file has changed, doesn't it?
I think it's just about help file that is not clear, nor is tooltip.
There's my thread that is related to this request: Copy UpdateExisting help file (no one answered)
The Copy command should deal with all possibilities, no matter how unlikely. I agree that this should never happen under normal circumstances but for whatever reason the user may have manually applied a time stamp (e.g. with a TOUCH command), so it's not impossible. Options that spring to mind are..
[ol][li]Propose to copy SOURCE to DEST, with the usual popup.[/li][li]Ignore. Do nothing.[/li][li]Pop up an error message and let the user choose to do nothing, or copy SOURCE to DEST, or copy DEST to SOURCE.[/li][/ol]
Option (1) is what happens currently. It presumes that SOURCE is the correct choice with no basis for such a presumption and does not alert the user to the dilemma. Option (2) "wimps out" and does not alert the user to the dilemma. My preference is (3).
