|
|
|||||||
Using KiXtart 2010 4.50 Code:
The kix2010 manual tells for the "Move" command that: Quote: But when moving to an UNC style path and when the destination file exists, the file is not overwritten. The Error Code is 80, telling it exists. |
||||||||
|
|
|||||||
The manual also states Quote: which you forgot. You're now tryig to write a file under the same location as an already existing folder. As windows does not allow this, an error message is generated and the action is not beign performed. This is the correct and desired behavior. Thus, it is a coding error in your code, not a KiXtart or windows bug. |
||||||||
|
|
|||||||
Code:
You are right, but I see no difference. In my example, the destination path exists. |
||||||||
|
|
|||||||
so, jens, this is a kixtart issue, no? |
||||||||
|
|
|||||||
This feature is still available in "KiXtart 2010 4.51 Beta 1" |
||||||||
|
|
|||||||
Also "KiXtart 2010 4.51 Release Candidate 1" is not overwriting when moving to a UNC style path. |
||||||||
|
|
|||||||
Sealeopard, what version where you using when testing this? Or did you simply quote from the manual? I've also done some quick testing with 4.50 and come to the same conclusion as the topic starter. So it appears not to be a RTFM issue afterall... The line in the documentation about the trailing backslash is obviously meant when moving directories and not for files. The overwriting comment is for doing something like this: Code: Move "D:\MyFolder\MyFile2.txt" "D:\MyFolder\MyFile3.txt" The above does overwrite without warning. So we have: a) a bug b) a minor documentation error "If the source or target specifies a directory, please make sure to add a trailing backslash." Should be something like: "When moving directories, please make sure to add a trailing backslash." Nice double catch Witto. |
||||||||
|
|
|||||||
moved the thread from suggestions to beta and asked ruud to comment on this. |
||||||||
|
|
|||||||
Cannot move folders over Shares Hello! I run into some difficulties when I try to move folders: This code works: Code: $src="c:\tmp\sourcefolder\" This one doesn't: Code: $src="\\server\share1\sourcefolder\" Error number and message are: Quote: I tried it with COM: Code: $fso = CreateObject("Scripting.FileSystemObject") and get no error in both cases (local and remote move) - but nothing happens... Can somebody please push me in the right direction? I prefer working with Shares. Thank you very much in advance. |
||||||||
|
|
|||||||
Does the MOVE command work from the commandline? I suspect it's not a KiXtart issue as even the COM object fails. |
||||||||
|
|
|||||||
Also 4.52 Beta1 not overwriting the target if
Code:
|
||||||||
|
|
|||||||
Move is still not overwriting in Kix32 4.52 and 4.53 Beta 1. |
||||||||
|
|
|||||||
Thanks for the report. MOVE indeed still has an issue with overwriting existing files if the target was a UNC. As it turns out, the underlying API returns a different resultcode for files accessed via a UNC. This is addressed in the next build of 4.53. Good one, thanks! Ruud |
||||||||
|
|
|||||||
Thanks, I appreciate all input that was given and I look forward to the new version. |
||||||||
|
|
|||||||
4.53 Beta 2 solved it. Thank you! |