>>Started getting this from FPD (just to tell you that it's not specifically VFP issue) in two situations - both were W95 networks, when a new server was added (in one case a W98, NT4.0 in the other), and the files were open on the old W95 server. The error was "Error reading file" and we tracked it to the files being suddenly closed without notice, server side. Then we had it sometimes on the NT server, but it was a half-successful installation, it was reinstalled soon and the error vanished. All these networks used NetBEUI and I think switching to TCP solved many other problems as well. Browse master setting in peer-to-peer networks also needed to be set to one machine enabled, all others disabled.
>
>I saw the behavior on TCP/IP w/ no other protocals loaded. It's definitly something on the server but what?

In NetBEUI W98/95 environment it occurred when there was one W95 BrowseMaster and the W98 was not. Actually everything worked fine, except the W98 machine was getting its files (open on w95 server) closed in mid-air, and long copies to/from the W95 server died after a dozen megs. We could monitor the files being closed for no obvious reason. The solution was to have BrowseMaster on one W98 machine enabled, and disabled on all others.

Wouldn't know why a reinstall in the NT case helped... maybe it's because this is the exact reason why God invented reinstalls?