Moving folders and sub-folders ?

I have tried using the FileSystemObject to move a folder that contains text files and up to 3 levels of sub-folders, but with no luck. I need to move the folder and everything in it from one server to another.

Does anyone have a working example of doing this ?

Or is there a better way ?

Thanks.

You should be able to use the MoveFolder Method of the FileSystemObject, but in some cases it make give you a Permission Denied Error when moving to another volume (or server), if this is the case use a 2 pass process, i.e

Code:

---

Private Sub Command1_Click()
    Dim oFSO As Object
    Set oFSO = CreateObject("Scripting.FileSystemObject")
    Call oFSO.CopyFolder("C:\Test", "D:\Test")
    Call oFSO.DeleteFolder("C:\Test", True)
    Set oFSO = Nothing
End Sub

---

Thanks Aaron.

That was exactly what was happening, and your solution works great. You saved me several more hours of frustration.

is copying slower than moving??

p.s. sorry to bring an old thread... but it's better to use this one rather than create a new one ...isn't it?

Quote:

---

Originally Posted by lplover2k

is copying slower than moving??

p.s. sorry to bring an old thread... but it's better to use this one rather than create a new one ...isn't it?

---

Moving is copying, then going back and deleting.

i was under the impression that moving just changes where the file is indexed in the filesystem - no actual data is moved, and it's certainly not copied and killed (unless it's across drives, I guess) - thus Moving is faster than Copying

Quote:

---

Originally Posted by bushmobile

i was under the impression that moving just changes where the file is indexed in the filesystem - no actual data is moved, and it's certainly not copied and killed (unless it's across drives, I guess) - thus Moving is faster than Copying

---

From an OS standpoint you are correct.

However, programmatically, from VB, you would have to use "FileCopy" and then "Kill" to perform a "Move"

Quote:

---

Originally Posted by Hack

From an OS standpoint you are correct.

However, programmatically, from VB, you would have to use "FileCopy" and then "Kill" to perform a "Move"

---

VB Code:

Name "C:\blah.txt" As "C:\text\blah.txt"

Quote:

---

Originally Posted by bushmobile

VB Code:

Name "C:\blah.txt" As "C:\text\blah.txt"

---

Good point....for some reason my aged brain never associated this type of code with anything but file renaming.

I think I'll go home and take a nap. :blush:

Quote:

---

Originally Posted by lplover2k

is copying slower than moving??

p.s. sorry to bring an old thread... but it's better to use this one rather than create a new one ...isn't it?

---

Actually, it would be best to create a new thread and post a link to the thread you are referencing. ;)

oh ok... will do that next time... why is bringing old threads bad...???

Well without going too far off topic, because it also sends out notifications to ever member that is subscribed to the thread for one. Another would be that in a way its thread hijacking - taking over someone else's thread topic. ;). And still, members will see the initial question and have to be bothered with reading the entire thread to find that it was solved and some addition/off topic question was asked when it would save them time to just have a new thread and read a single post. :)

another reason: if you jump on a RESOLVED thread, then most people aren't going to bother looking at it.