Professional administrators have done this sort of thing years ago. You can manipulate the date in batch scripts without the need to use VBscript or something like that. The trick is to understand the conversion to Julian date. The DOS DATE command does not do Julian date number, but you can convert it and do some add or subtract and come up with an answer.
So you need to convert to a julian date, do the addition, and then convert back. just leverage both batch and VBScript at once.
C:\Users\BC_Programming>for /f "tokens=*" %P in ('cscript /NOLOGO temp.vbs') do
set newdate=%P
@echo off
echo WScript.echo(time+(1/24/60)) >> temp.vbs&&for /f "tokens=*" %%P in ('Cscript /NOLOGO temp.vbs') do set newdate=%%P
del temp.vbs
after running this, the newdate variable will have the current time plus a minute. Note there isn't a huge advantage between this solution and gregs; the only difference is this one can easily be told to use the entire date by changing time to now, whereas the pure batch solution will then need to have a lot of checks for overflows to the next date,month, and year.
But you need to define what a 'month' is. Often when people say 'in a month', they mean exactly 30 days.
Er... No. They almost always mean the same date in the following month. Depends on the context, though.
For example, if it's the 12th, and somebody says, "in a month" they might mean the 12th of the following month, or they might mean 30.
I think the most important thing here is that we are adding minutes, so it really won't matter how long a month is; it might if we were considering a complete Date/Time, but the OP only said the current time... so we go with that.
