Solved Moving files with a bat-file

Hey guys,

a hopefully quick question. I need a batfile that is executed in a folder without using the path. I'd put it into a gazillion other folders later and execute it everywhere. So, in a given folder are two subfolders, A and B. All files from B should move to A. THat is all, but I cant get it done for the life of me.

Its this command (from a MS-page)

Examples​

To move all files with the .xls extension from the \Data directory to the \Second_Q\Reports directory, type:

move \data\*.xls \second_q\reports\



So, this is the correct syntax. What I do is this:

move \b\*.* \a\

The folders already exist, nothing is overwritten (they are testfolders anyway). The batfile is executed from the main-folder that contains the folders a and b. Please no other suggestions how to do this, this is about the syntax within this specific example, the actual problem is try to solve is way more complicated.

It just... doesnt... work... A window is opening, but closing immediately, so I cannot see an error. Where am I was being stupidly?

First, so that you can see the error message without the window closing do this:

Rather than running the command by double clicking on the batch file open up a command prompt first. Then change directories to the location where the batch file is by typing in CD \<path_to_batch_file> and then hit ENTER. Then type in the name of the batch file and hit enter. Because the command prompt is already open it won't close on you when the batch file is run, and you will be able to see any messages that are output.

Secondly, I see that you are using paths such as \B and \A. The \ indicates the root of the drive. So, what you are actually specifying is a folder by the name of B or A located right off the root of the drive. You mentioned that you want to be able to run this batch file inside of any particular directory so you should use relative paths. As an example:

".\A" or ".\B". The period denotes the current directory so ".\A" Indicates a subfolder called "A" beneath the current directory.

You might also want to include "cd /d %~dp0" near the start of the batch file. That causes the batch file to change directories to the location from which the batch file is being run. Then other paths can be specified as relative paths to the current folder. So, putting it together, you end up with this:


The result of this would be that any files with a .XLS extension in a subfolder called "data" will be moved to a subfolder called "second_q\reports".

If any of this is not clear or if you need further help with it, please do let me know.

Run those commands within a cmd prompt and you'll probably see the problem better.
I do not think that the bits of syntax that you have posted can possibly be correct. Your cmd prompt test will confirm that.
Batch script is not designed with relative paths in mind. All I should have said is that I have experimented with it but do not have a single example of using it for real.
If you provided a link to the MS page you looked at, people might be able to suggest what you have misread on that page [if that's the case].

I am not at all clear what you are trying to do.
Do you want to stick the batch file wherever it suits for for each use and move something in a specific subfolder of wherever you have stuck the batch file on that occasion?
The subfolder names will always be the same?


Denis

Thank you. So I missed a single "."

But before I close the thread. I don't understand the cd /d %~dp0-part. I have a mainfolder with subfolders and even without that command I can copy files from one subfolder to the other. The "." seems already to give the command that the executing folder is the one the bat-file is in. So... what would be a case where you need "cd /d %~dp0"?

@Try3
That was the page. I am not really into reading stuff like this and I might have made a mistake.

But its all done already. I know what I have to do, thanks.

I was slow to start responding and had not seen that Hannes had already replied.

But, for future, reference SS64 generally provide better explanations & guidance than MSLearn
e.g.
Move - SS64

If you are trying to learn about more than just the current example then read
my ditty - Batch file and PowerShell guides [post #7] - ElevenForum


Denis

Try3 said:

Batch script is not designed with relative paths in mind.

Click to expand...

Batch files work perfectly with relative paths. I have entire programs written as nothing more than huge batch files referencing literally dozens of relative paths, all running flawlessly.

Samun said:

Hey guys,

a hopefully quick question. I need a batfile that is executed in a folder without using the path. I'd put it into a gazillion other folders later and execute it everywhere. So, in a given folder are two subfolders, A and B. All files from B should move to A. THat is all, but I cant get it done for the life of me.

Its this command (from a MS-page)

Examples​

To move all files with the .xls extension from the \Data directory to the \Second_Q\Reports directory, type:

move \data\*.xls \second_q\reports\



So, this is the correct syntax. What I do is this:

move \b\*.* \a\

The folders already exist, nothing is overwritten (they are testfolders anyway). The batfile is executed from the main-folder that contains the folders a and b. Please no other suggestions how to do this, this is about the syntax within this specific example, the actual problem is try to solve is way more complicated.

It just... doesnt... work... A window is opening, but closing immediately, so I cannot see an error. Where am I was being stupidly?

Click to expand...

A useful debugging technique is to put "pause" at the end to hold the window open.

Ben

Samun said:

I don't understand the cd /d %~dp0-part.

Click to expand...

That command changes the drive and directory to the location in which the batch file resides. That way, when you reference a relative path it will be relative to the location of the batch file and not whatever location the batch file was referenced from.

Think of this as if you were manually entering commands. For example, say you manually ran this command:

dir

That would list the directory contents of the folder from where you ran the command. However, what if you wanted to list the contents of a specific folder such as D:\MyFolder? Then you could do either one of these:

dir D:\MyFolder

OR

D:
CD \MyFolder
dir

In a batch file, the cd /d %~dp0 is like running the first two commands in the 2nd example above without having to know the path to specify. If substitutes the location of the rive letter and the path where the batch file is physically located so that yu can run that batch file from anywhere without having to change the path (as you said you wanted to do).

I am going to veer off topic just slightly here. When you are experimenting with commands to move and copy files my personal preference is to use robocopy. Robocopy has a switch that will simulate the action that you are asking it to perform without actually carrying it out. This is great for testing so that you don't accidentally move or delete files unintentionally. It will act as if it is carrying out the command and display output as if it was running the command without actually doing it. It's perfect for debugging and testing. I realize that the syntax of the robocopy command can be a little bit daunting at times but it's well worth learning.

Example:

robocopy D:\Source D:\Destination /MOVE

This command will move all files and subfolders from D:\Source to D:\Destination. Now, modify the command by just adding "/L" like this:

robocopy D:\Source D:\Destination /MOVE /L

The "/L" tells robocopy to SIMULATE the action so that you can see exactly what it would do IF you actually ran the command but without moving or copying anything. Great for testing and experimenting in complete safety!

Interesting. I will bookmark this in case I need this.

Thank you all for the help. (closed)

Try3 said:

But, for future, reference SS64 generally provide better explanations & guidance than MSLearn

Click to expand...

Very helpful link!

FWIW, I like to copy files to the destination and insure they all got there before removing them from the source.