Gaylen,

I've had a similar problem when copying a file to an Iomega Zip drive, if the access was very slow. What would happen was:-

VFP -> ZIP (via OS) "create file x"
ZIP ->VFP "File Created"
VFP ->ZIP (via OS) "does file exist"
OS -> VFP "No" (but ZIP drive is still whirring and writing the file, which is created correctly, etc.).

...although the file exists on the ZIP drive. This only happened when access to the Zip drive was slow, as if it had replied that it had created the file when in fact it was in the *process* of creating the file (and the file was buffered somewhere) so VFP continued to the next statement.

Perhaps the network / comms line was particularly busy for these six sites (as I think Sanjay suggested) and you ran into a similar problem, perhaps related to NT buffering (just guessing). You could try putting a pause before testing for the file, calling doevents() or putting the error routine into a loop.

Just a suggestion.

------
>Sanjay
>
>Just to clarify
>
>The files are being sent from the local properties via a network connection to headquarter. The program went out to over 200 locations. All worked fine except 6 location which got the 1102 error message. However those 6 locations actually transmitted their daily report files and were received by Headquarter even though the on error routine gave then an error message. The problem is why is the error message being invoked if the file transfer actually worked.
>[snips]