6 replies to this topic

[oriensol]

Looks like FileCopy copies extra files under certain circumstances.

Here's an example:

Run this in CodeBox:

FileCopy,"D:\TestInput\testfile.*","D:\TestOutput"

with the content of D:\TestInput being:

d:

cd TestInput

dir /s *

Volume in drive D is WORK

Volume Serial Number is 40C5-6EEB



Directory of D:\TestInput



10/15/2009  01&#58;44 PM	<DIR>		  .

10/15/2009  01&#58;44 PM	<DIR>		  ..

10/15/2009  01&#58;30 PM	<DIR>		  junk

10/15/2009  01&#58;29 PM				 0 testfile.txt

			   1 File&#40;s&#41;			  0 bytes



Directory of D&#58;\TestInput\junk



10/15/2009  01&#58;30 PM	<DIR>		  .

10/15/2009  01&#58;30 PM	<DIR>		  ..

10/15/2009  01&#58;30 PM	<DIR>		  junk

10/15/2009  01&#58;29 PM				 0 testfile.txt

			   1 File&#40;s&#41;			  0 bytes



Directory of D&#58;\TestInput\junk\junk



10/15/2009  01&#58;30 PM	<DIR>		  .

10/15/2009  01&#58;30 PM	<DIR>		  ..

10/15/2009  01&#58;29 PM				 0 testfile.txt

			   1 File&#40;s&#41;			  0 bytes



	 Total Files Listed&#58;

			   3 File&#40;s&#41;			  0 bytes

			   8 Dir&#40;s&#41;   1,742,062,592 bytes free

You will get the output (with both 77RC2 and 78SP2):

d:

cd TestOutput

dir /s *

Volume in drive D is WORK

Volume Serial Number is 40C5-6EEB

 

Directory of D:\TestOutput



10/15/2009  01&#58;44 PM	<DIR>		  .

10/15/2009  01&#58;44 PM	<DIR>		  ..

10/15/2009  01&#58;43 PM	<DIR>		  junk

10/15/2009  01&#58;29 PM				 0 testfile.txt

			   1 File&#40;s&#41;			  0 bytes

 

Directory of D&#58;\TestOutput\junk



10/15/2009  01&#58;43 PM	<DIR>		  .

10/15/2009  01&#58;43 PM	<DIR>		  ..

10/15/2009  01&#58;43 PM	<DIR>		  junk

10/15/2009  01&#58;29 PM				 0 testfile.txt

			   1 File&#40;s&#41;			  0 bytes

 

Directory of D&#58;\TestOutput\junk\junk



10/15/2009  01&#58;43 PM	<DIR>		  .

10/15/2009  01&#58;43 PM	<DIR>		  ..

10/15/2009  01&#58;29 PM				 0 testfile.txt

			   1 File&#40;s&#41;			  0 bytes



	 Total Files Listed&#58;

			   3 File&#40;s&#41;			  0 bytes

			   8 Dir&#40;s&#41;   1,742,061,568 bytes free

whereas, I would have expected to see ONLY ONE (testfile.txt) file in D:\TestOutput.

FileCopy seems to be copying all files that match the filename within subdirectories also - seems to be something to do with the use of '*'.

Thanks.

[paraglider]

Both directory lists look the same to me

[was_jaclaz]

Both directory lists look the same to me

They ARE the same.

Point is if that should be the effect of the command:

FileCopy,"D:\TestInput\testfile.*","D:\TestOutput"

what oriensol expected was a result like this:

d:

cd TestOutput

dir /s *

Volume in drive D is WORK

Volume Serial Number is 40C5-6EEB



Directory of D:\TestOutput



10/15/2009  01&#58;44 PM	<DIR>		  .

10/15/2009  01&#58;44 PM	<DIR>		  ..

10/15/2009  01&#58;29 PM				 0 testfile.txt

			   1 File&#40;s&#41;			  0 bytes

WITHOUT the creation of the /junk and /junk/junk subdirectories AND files in them.

jaclaz

[Lancelot]

FileCopy,"D:\TestInput\testfile.*","D:\TestOutput"

.............
whereas, I would have expected to see ONLY ONE (testfile.txt) file in D:\TestOutput.

I guess you should use

FileCopy,"D:\TestInput\testfile.*","D:\TestOutput",NOREC

FileCopy seems to be copying all files that match the filename within subdirectories also - seems to be something to do with the use of '*'.

for backward compatibility wildcards copy recursive

check
http://winbuilder.ne...x.html#FileCopy

[oriensol]

Thanks Lancelot. I wasn't aware of the functionality - did not seem obvious.

[was_jaclaz]

Case solved.

Thread renamed.

NOT a bug, it is by design .



jaclaz

[paraglider]

The behavior of FileCopy is fully documented here:

http://winbuilder.ne...x.html#FileCopy