Re: Copy Script
- From: "TDM" <rpuffd@xxxxxxxxx>
- Date: Thu, 28 Jun 2007 14:03:33 -0700
"ickleric" <home@xxxxxxxxxxxx> wrote in message
news:1182955670.354541.47650@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
Ahh briliant. I knew it would be something simple. Also had to move
the create computername folder out of the For Each loop, as i only
needed to create it once.
On another note, if the script fails because a file is in use or a
filename is too long, is there anyway to log exactly what caused the
script to fail on i.e. filename/path?
The exact reason I never use CopyFolder anymore in my data
backup and data migration scripts. I know of no way to figure out
where it failed, let alone continue the copy after the error. The same
goes for the CopyHere method. So, I use good old Xcopy to get
the job done. It will continue on error, and you can get access to
the error's during copy via StdOut if you use the .Exec method to
run your Xcopy.
TDM
.
- Follow-Ups:
- Re: Copy Script
- From: Tim
- Re: Copy Script
- References:
- Copy Script
- From: ickleric
- Re: Copy Script
- From: S Moran
- Re: Copy Script
- From: ickleric
- Re: Copy Script
- From: ickleric
- Re: Copy Script
- From: Tim
- Re: Copy Script
- From: ickleric
- Copy Script
- Prev by Date: Re: Copy only archivable items
- Next by Date: Re: Using a WMI object from with a webpage
- Previous by thread: Re: Copy Script
- Next by thread: Re: Copy Script
- Index(es):
Relevant Pages
|