6 Jun 12 14:32
Constantly monitoring a directory for file changes via a vbscript will consume too many clock cycles and will likely bog down the computer. However, if you run the script as a service or compromise on the frequency at which the folder is monitored, say every 5 seconds, then the job is more feasible with vbs.
Break down the problem into smaller parts.
a) Check for changed files. This can easily be accomplish by acknowledging that the ANY file change will have the most recent modified timestamp. Simply traverse a folders file and look for the most recent modified date. Then compare that date with the previous obtained modified date. If it's more recent, there has been a change.
b) Check for changes in folder content. This is a little more intensive but still fairly easy. All you need to do is compare a list of files generated at point-in-time A with a list of files generated at point-in-time B. The differences will be the files that were either added or removed.
Are you familiar with vbs enough to figure out the code? The following link may help:
"I hope I can chill and see the change - stop the bleed inside and feel again. Cut the chain of lies you've been feeding my veins; I've got nothing to say to you!"
"I do not offer answers, only considerations."
- Geates's Disclaimer