Rob,
Sometimes works sometimes doesn't, have checked the paths and all ok. It
seems to be a timing issue when using UNC network paths, if I have a couple
of explorer windows open one each for the source/destination then all works
fine otherwise seems to be a 50/50 chance of returning the OLE error. I
suspect the FileSystemObject may be ok with local files but is too flaky for
production use over the network.
Cheers,
Nick
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf
> Of Rob Anderson
> Sent: 01 September 2006 14:19
> To: ProFox Email List
> Subject: RE: Move directories
>
> Also, this one :-
>
> http://www.tek-tips.com/viewthread.cfm?qid=1106669&page=1
>
> Robbo
>
>
>
> -----Original Message-----
> From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On
> Behalf Of Nick
> Sent: 01 September 2006 13:52
> To: 'ProFox Email List'
> Subject: RE: Move directories
>
> Rob Anderson suggested:
>
>
> > How about something along the lines of :-
> >
> > o = CreateObject("scripting.filesystemobject")
> > o.CopyFolder("c:\cvp", "t:\")
> > o.DeleteFolder("c:\cvp")
>
> Works ok for small tests but not robust enough for use in a real
> application.
>
> For example:
> o = CreateObject("scripting.filesystemobject")
> o.CopyFolder("\\Server\Data\Documents\Test2",
> "\\Server\Archive\Data\Documents\Test2")
>
> Fails with OLE error code 0x800a004c. Unknown COM status code.
>
> Any ideas why?
>
>
>
[excessive quoting removed by server]
_______________________________________________
Post Messages to: [email protected]
Subscription Maintenance: http://leafe.com/mailman/listinfo/profox
OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech
** All postings, unless explicitly stated otherwise, are the opinions of the
author, and do not constitute legal or medical advice. This statement is added
to the messages for those lawyers who are too stupid to see the obvious.
