|Time is definatly easier, indeed.|
I like the solution you posted Nbrane, but keep in mind that it does have some serious drawbacks, and the biggest one being the fact that the script itself (that what you put into the scheduling) does NOT contain the 1-hour rule.
You are allowing the wrapper (super-script feature, by means of scheduler) take over that task. Now, if that one fails (scheduler down, server down, scheduler blocked, ...) the script itself may behave weird on it (and basically, not take only the files within the 1-hour rule). You must always have any constraint, as close to the core as possible, so that any running of it, uses that constraint.
Dngood, if you want to, I'll write a script to help you with it. But, there's a catch, being that I will rely on other scripts I have (the ones handling the time), so in other words, it'll be a collection of scripts. What I would do, is to write 1 script, that can do the following :
Copy 1 file to another folder, only if the file is less than one hour old. It'll be something like:
xcopytime.cmd C:\source\test.jpg C:\target 60
Which would copy file C:\source\test.jpg to C:\target but only if the file is "less than 60 minutes old". To check on the "age" of a file, I'll need to call other script, which are custom.
Let me know if you want this.