Search results for query: *

>Windows Resource Kit Can't have any of that sort of dodgy software infecting our system. [smile]

Thanks, not the answer I was hoping for, but somewhat expected. I'll let someone else bash their head against the ROBOCOPY brick wall, and accept the time delay for now. Any advise regarding using cmd shell copy compared to vbscript copy for the actual file copying?

Update3: I thought the order of the file comparison may be an issue, as "same" (which is most common) was the last test after all others (size and modified) were false. I reorganised that block If objSrcFile.DateLastModified = objDestFile.DateLastModified Then If objSrcFile.Size =...

Update2: removed the wscript.echo commands and time now dropped to 10 secs. Couple of general questions: 1. Are compound commands (eg If Not objFSO.FileExists(Replace(objDestFile.Path, strDest, strSrc, 1, -1, vbTextCompare)) Then faster than multiple commands eg strSrcFile =...

Update: I removed the log concatenation, and now just return an empty string from the function. Time has dropped from 20 secs to 15 secs, which is good improvement but nothing like ROBOCOPY's 1 sec. Is it worth creating separate thread for each top level folder? Cheers

Hi, I am a self taught vbscript user, and have a VB script that is used to maintain local copy of server data on laptop for access when disconnected. This runs on a system with limited access (can't add executables), but I can use vbs. I have been using ROBOCOPY to do the grunt work of mirroring...