I don't have enough familiarity of how the FileSystemObject works under the hood, so to speak, so I'll ask here...
I know that if I use the DOS COPY or XCOPY commands to copy a file from one folder on a server to another folder on the same server, it will pull the file over to my workstation and then copy it right back over the network connection to the specified folder. I have numerous large files and I can't tie up the server that way. So... If I instead use the FSO.Copy command and specify that it copy the file to another folder on the same server will it accomplish it without sending the file back and forth over the network connections?
My primary goal is to reduce network congestion and consequent time delays. If FSO won't do it, what will? I'm still trying to (1) run it from a workstation and (2) use it for the future when I begin using a Filer rather than a Server.
I know that if I use the DOS COPY or XCOPY commands to copy a file from one folder on a server to another folder on the same server, it will pull the file over to my workstation and then copy it right back over the network connection to the specified folder. I have numerous large files and I can't tie up the server that way. So... If I instead use the FSO.Copy command and specify that it copy the file to another folder on the same server will it accomplish it without sending the file back and forth over the network connections?
Code:
Const OverwriteExisting = True
Set objFSO = CreateObject("Scripting.FileSystemObject")
objFSO.CopyFile "\\MyServer\FolderA\my.txt" , "\\MyServer\FolderB\", OverwriteExisting