See this Comm Center thread (R. Post), as well as this one (L. Owings). Now that Owings is seeing this on a "fast" machine, I believe that there is a race condition in the Scripting.FileSystemObject where I am creating a file, with overwrite right after opening and reading it all. Then the new file is immediately written and closed. Somewhere in there is a race. Post got it with a Solid State Drive.
Put delays in there. |