>I just returned from visiting a client that was experiencing a larget number of Invalid Seek Offset and Error Reading File errors. I started off looking at all the well known causes (corrupt files, printer drivers, video drivers, etc.) and finally found the cause but not the problem.
>
>It seems that the problems occur because the file server no longer has the files open. Either something is causing NT to close all the files held open by the workstation or the connection is being dropped and then the workstation is automatically re-connecting to the server.
>
>It's definitely a problem on the server. We moved the VFP database to another server and the problems no longer occur. So my question is whether anyone has experienced this before and if so, what was the cause and how was it solved?
>
>FYI - The server was an HP NetServer with four Pentium Pro 200 processors and 1GB of RAM. The server is only hosting two apps: this one and another called Data Works.

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.