I have done this in the past, with the result that the new folders and files are copied to the local drive as I intended. My intent is to merge the files from the source drive into the local target drive without rewriting the files that are common to both drives. The folders do not exist in the local target drive, but are present in the remote source drive.īoth drives are starting from the same parent directory. As the folder names are somewhat sensitive, I have edited them to "DIR1" and "FOLDER", but the original names have no special characters or anything out of the ordinary. Is there a setting I am overlooking, or is this a flaw in the download routine? So, you may ask, 'why not use source file newer'? Because the repository was recently moved to a new server, and all the file dates are very recent. If I change the default 'file exists' action to "overwrite if source file newer", the download is stored properly. I have made certain that the local pane is pointing to the target directory.
However, when I look at the target directory, the new file does not appear in the list. When I run the download, it appears to be behaving as expected, showing that new files are being downloaded. I set the default "file exists" action for downloads to "skip file" if the remote file is the same as the file on my drive. I want to be able to download only files that I do not already have in order to keep a local copy of its contents. I'm having a problem when trying to download new files from a file repository.Ī group of users maintains a file repository and adds files from time to time.
0 kommentar(er)
