@ Shadow Wizard: Would you like to see archive bits on folders as well? I tend to avoid using them because I feel as though I’m forced to assume that the folder contents are all set as well….and if I don’t want to assume, I check, and that defeats the purpose of using an archive bit on a folder anyway. It also seems to me that most backup routines rely on the file level bits anyway. What’s your take?

The code is efficient and the way you approached the situation is rather amazing.

Keep up posting proactively and all the best.

Regards,
Tony

Let me take your suggestions in order. First, I didn’t feel it necessary to include a message when the code completes, because it isn’t actually intended to run as a stand-alone script. It’s designed to be incorporated into a full backup scheme. In that case, no notification would be necessary.

As for your second, suggestion, the original code sample for this post actually does contain recursion. I left it out of this sample for sake of brevity. However, I’ll do a follow up post to show how this can be included so stayed tuned for my next blog!

Two suggestions though: add some sort of message when the code finish successfully, and also what about recursive code that will set archive bit on all files in folder plus all files in all sub folders? this can be pretty cool addition to the code.