>Thanks Craig. I'll pass this message along to our hardware guys but they maintain there is nothing wrong with the network or the cabling. The strange thing is that the other program that also uses the mapped drive never has these errors (except right after the transfer program errors out).
>
>I was just reading on another thread that it's suggested to put "tmpfiles='c:\temp'" into the config.fpw to force the program to create temp files on the local drive to get rid of these errors. Worth a try. This is making me nuts ;-).

One way that I have proven to "network" guys that it is the network is by copying large amounts of data outside of the application, just using Windows drag and drop. If there is an error then you can say, "If Windows can't do it, my app can't do it, fix the network!".

Good luck, I HATE 1104's.