China DOS Union

Using date to get the time and date. I now want to get the next working day date of the system. For example, today is Friday 20070406, and I want to get next Monday 20070409. If it is Thursday 20070405, I need to get Friday 20070406. I don't know how to implement it. I don't know how to do arithmetic operations on dates, and also don't know how to judge the day of the week.

dim Wday,today

today=date

Wday=Weekday(now)

Select Case (Wday)

    case 1 today=today+1

    case 2 today=today+1

    case 3 today=today+1

    case 4 today=today+1

    case 5 today=today+1

    case 6 today=today+3

    case 7 today=today+2

end select

WScript.echo "The next working day is: "&CDate(today)

Try this?

```batch code
@echo off & setlocal enabledelayedexpansion
set condate=20070407
set today=%date:~0,4%%date:~5,2%%date:~8,2%
set /a num=%today%-%condate%
set /a num=!num!%%7
if %num%==0 set /a num=!today!+2&goto today
if %num%==1 set /a num=!today!+1&goto today
if %num%==2 set /a num=!today!+1&goto today
if %num%==3 set /a num=!today!+1&goto today
if %num%==4 set /a num=!today!+1&goto today
if %num%==5 set /a num=!today!+1&goto today
if %num%==6 set /a num=!today!+3&goto today

:today
echo The next working day is: !num!
pause
```

There is no universal code..

The formats in XP and 2000 are different.

As for date calculation, it's an algorithm issue. It has nothing to do with here.

As for the day of the week, %date% already contains it.

Thanks to friend wudixin96. The VBS script on the second floor seems to be usable. There is an issue with the script on the third floor; it will have problems if there are years in between. I wonder if this problem can be solved? Or how I can get the variables of the VBS script in the bat script, is it possible??

[ Last edited by lililulula on 2007-4-8 at 04:27 PM ]

Bump for myself first, and by the way, digest the script on the 3rd floor~~~

It's too cumbersome to write like this..

You can use the system's own functions for analysis...

Assume the operating system is Windows XP..

Then the following script can be used. (Here, error judgment is not carried out, and time judgment is not done on the spot. When using 23:59:59 seconds, it will cause the date to return an error.)

@echo off
set OldDate=%date%
:reInput
echo Please enter the date you want to query. The format is: 2007-04-05.
set /p input=>
echo %input% | date >nul
if not errorlevel 1 (
echo The next working day is: %date:~11,3%
) else (
goto :reInput
)
echo %OldDate% | date >nul
pause

Oh.. This script can query dates that are any date supported by the XP system. If not used at a specific time point, this script is basically error-free.

I haven't looked closely at the title of the original poster. Actually, it's also very simple.

I once posted about arbitrary date calculations, which can query any year, month, and day (similar to an almanac).
But everyone didn't seem to like it, so I deleted the post.
Date calculation needs to define time.

Friend flyinspace, your script on floor 7 only checks what day of the week the input date is. But I still have questions about the two lines echo %input% | date >nul and echo %OldDate% | date >nul. I don't quite understand. The | date>nul after that is supposed to empty the obtained date? But when I simply test set /p input=:> echo %input% | date>nul, the input date will be modified to the current system date. However, in the script, after adding echo %OldDate% | date >nul, the system date won't be modified. I don't really understand the specific meaning. I hope friend flyinspace can tell me.

And my requirement is to get the system date and then judge the next working day, and get the date. The script on floor 3 will have errors during the year-end, I don't know what methods there are to solve it.

The problem has been solved. The 2nd floor told me how to do date arithmetic operations. I got inspiration from it. Because the thinking method of the 2nd floor would be wrong when crossing years during script running, so I directly judge the week character, which avoids this problem. The script is as follows (under 2000):
@echo off
set day=%date:~-10,4%%date:~-5,2%%date:~-2,2%
set date=%date:~-14,3%
if %date%==Monday set /a nextworkday=%day%+1&goto workday
if %date%==Tuesday set /a nextworkday=%day%+1&goto workday
if %date%==Wednesday set /a nextworkday=%day%+1&goto workday
if %date%==Thursday set /a nextworkday=%day%+1&goto workday
if %date%==Friday set /a nextworkday=%day%+3&goto workday
if %date%==Saturday set /a nextworkday=%day%+2&goto workday
if %date%==Sunday set /a nextworkday=%day%+1&goto workday
:workday
echo The next working day is: %nextworkday%
pause

There is another problem: why does the variable name have to be date to be effective when setting date multiple times? For example
set date=%date:~0,10%
set date=%date:-=%
The date variable is today's date 20070409
But if it is like this, it is invalid
set day=%date:~0,10%
set day=%date:-=%
The date is 2007-04-09, and the second set is invalid
Enabling delayed variables doesn't help

[ Last edited by lililulula on 2007-4-9 at 12:36 PM ]

Your system is Windows 2000.

When using my script, there should be an error prompt: no operand.

set date=%date:~-14,3%
Also, it is best not to define existing environment variables.

The error in the next year is because there is no judgment on the year. (There are differences between leap years and common years) And there will be deviations in the first week of each year...

Also, no matter how I look at it, this script should have problems.

Even within 2007, there will definitely be some days with errors.

The time judgment is not strict enough.

Friend flyinspace, the script you mentioned for the second floor does have issues. If I judge by the day of the week, taking the current day of the week and comparing strings, it should be fine because I'm just taking the system's subsequent day of the week, and there are only 7 possible cases when judging~~~~ Also, I don't quite understand what you mean by not defining existing Huangjing variables?

[ Last edited by lililulula on 2007-4-9 at 01:28 PM ]

It is suggested that you read the batch processing tutorial first.

I will point out your problem.

Assume it is April 30, 2007.
Then how to judge?

You're right when you say that. Later I also saw that the script on floor 2 has this problem, and my script also has this problem. However, the VBS script on floor 3 is okay, as it has the built-in parameter wekekday~~~~ It seems I didn't consider the problem comprehensively. Thanks for the reminder from the upstairs. I want to know if there's a way to solve this problem? Or how to get the value of the variable in the bat script from the final &CDate(today) in VBS???