>>You told John there is a secondary process running - what is it?
>
>A secondary process scans the destination directory until it sees the file. If the file is there, it tries to copy it elsewhere. So, it sees the file being copied. And, it seems it successfully succeed to get a hold on it to try to process it while the file is being constructed.
Do you have any control over the secondary process? Can it be configured to wait XX seconds after seeing a new file appear, before it tries to copy it?
If this is the root cause of the problem, why is it not happening with *all* the files you copy?
Regards. Al
"Violence is the last refuge of the incompetent." -- Isaac Asimov
"Never let your sense of morals prevent you from doing what is right." -- Isaac Asimov
Neither a despot, nor a doormat, be
Every app wants to be a database app when it grows up