I'm working on a project that uses the System.IO.FileSystemWatcher to monitor a folder. What I'm wanting to do is copy select types of files from the monitored folder when they are created. This works pretty slick, but the problem I run into is that the FileSystemWatcher event oftentimes fires before the file finishes copying, so copying the file results in an error. I resolved this by creating a timer that's started on the FileSystemWatcher.created event. It waits a reasonable amount of time and then copies the file. No issues. My problem is that this isn't a very good solution, particularly when hundreds or thousands of files are being copied onto the watched drive, as this can result in thousands of threads. I wanted to resolve this by having the FileSystemWatcher.created thread add the files to be copied to an arrayList, then have a separate single thread monitor the array... wait for the file to be available to be copied, then start copying files. However this has more problems since the arrayList collection is changed on a separate thread which introduces a lot of locking issues, which I'd rather avoid. Can anyone offer an idea of what the best practice for this situation would be? I appreciate any input. :laugh: Thanks! Dana