Sanjay/Robert

I would like to thank both of you for your help and to bring you up to date on the problem I had with sending file from the field locations to Headquarters and getting an error message, even though the files were actually transferred.

The culprit turned out to be not enough NT licenses were available. Once they increased the number of licenses the problem went away.

The client and I both say Thanks Again for your help and guidance.

Gaylen



>>>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.
>
>Hi Gaylen,
>
>If you are using TCP/IP (most likely) as your comms protocol, what really should happen is that NT creates a temporary buffer for the info packets coming down the comms line until TCP/IP confirms that all packets have been successfully transmitted. It also allocates a pointer to this buffered area.(TCP/IP may not transmit data in packet sequence ie you may receive packet 4 of 6 before packet 1 of 6)
>
>Once NT's kernel is aware of all data received, all it does is re-writes the FAT entry of the pointer of the original file with the new one its just buffered. It will then send a message to the requesting app that the operation is complete, and from there, the app itself assumes charge. (All app requests go through to the NT kernel which handles the request.) If your call comes to test if the file's written comes too fast (as Robert's pointed out) you could perhaps be out of sync somewhere!
>
>Just a theory. That's all!