>Len,
>We had a LOT of strange problems which were caused by an overloaded NT network. Basically, the server would occasionally skip a command or not send a file if it got too busy. This sounds very much like what you're seeing - as the network gets too busy it can't keep all the commands straight.
>
>The SysAdmin removed an extremely heavy print application to a separate print server and upgraded our server (don't ask for details, I was only working on the various applications for that client) and we had substantially better results.
>

Server buden is a significant issue, and there's a great deal to properly tuning an NT Server. fortunately, there are good tools like PerfMon built into NT Server to help with the task. the study guides for the MCSE certification for NT Server and NT Server Enterprise cover this is in some detail, and there are whitepapers on tuning NT server buring in Microsoft's techNet documents on their web page. There is some discussion of tuning in John Saville's NT FAQ web page as well.

>Barbara
>
>>Has anyone experienced abnormal errors copying large number of records from one database to another when the database resides on a Microsoft Network (NT) versus a local hard drive? We encounter no problems at all using the same database on a local drive -- but as soon as we move it up to the network, and copy records from the net to the net, we get errors like "Error writing to file". To our knowledge -- we never had a problem when we were on a Novell network, although the database has grown a little since that time. Any help would be greatly appreciated.