Why depend on two asynchronous processes?
Can the process that generates the files log when it's done, and then the process that uses the file checks that log? Make it an actual workflow instead of two processes?
If that's not possible, PowerShell or any .NET scripting component can check files against a provided list and validate their existence.
But even with that, a large file can "exist", but still be in-flight on being written. If you start a second process on a file that's still being written to, you can end up with corruption or other errors.
That's why an actual workflow is definitely better. If it can be done.
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon