Hi Tim,

>Initially I thought that your code was very 'wordy' but on reflection,
>it is easy to see where changes would be needed if one was running mm/dd/yyyy format.

Correct, one simply swaps "4" for "7" and vice-versa in the "set month" and "set day" lines.   The StackOverflow site was where I found the code snippet I used (I stripped out all the echos once I'd  debugged my code), took me a bit of time to learn to count characters from zero, not 1, when setting up date selection (see, I didn't claim to be sharp  ! ).  So if I add a couple of rem lines, that should explain changes needed.  I confess I didn't think about making the batch file environment-independent - I was happy just getting it working reliably on my machines here in Australia.  (It's also why I placed the post in the Implementation rather than the User forum.)


rem on next line use 7 for AU date format or replace with 4 for US date format
set month=%date:~7,2%
if "%month:~0,1%" == " " set month=0%month:~1,1%
rem on next line use 4 for AU date format or replace with 7 for US date format
set day=%date:~4,2%
if "%day:~0,1%" == " " set day=0%day:~1,1%


On my system, once the backup is done once daily (at 7am), I now copy the file (a command in the batch file) to both a local external hard drive and also to my dropbox folder.  Then at my offsite location, I schedule a copy at noon from my dropbox folder to a local hard drive folder.  (This in case I forget to changeover the external hard drive at work on a regular basis).

"Poor man's" automation, I know, but I'm performing and saving more backups now than I've ever done before: local, offsite and "cloud" copies. And all without purchasing / installing extra software.

Yuri.