>>
>You can create the secont (control) file after upload/copy is complete. It could be just emty file with specific name and extension.

I've considered that approach...my situation is different than Ravi's, in that I have a legacy app (in business basic) that would create a bunch of little files. When each invoice is printed, if it meets a certain criteria (an EDI invoice, specifically), I would have it create a file containing its data. The fopen() test may work in this case, just haven't tested it yet.

The old app wouldn't take long to write each individual file, but I don't want to grab one unless it is complete.