I'm getting random Error Reading File errors on workstations connected to
NT Terminal Server. We're using VFP 6.0 with the latest VFP service pack on
Windows 2000 on the workstation and NT Terminal Server.

In my investigations, there are no locks on any files.

The strange thing about this problem is this: On the problematic
workstation, I can suspend at the point of the error and, using ALIAS(),
determine the active, problematic table. If I type the SET command to bring
up the view window or BROWSE to view the table, I get Error Reading File and
the VIEW window will NOT open. If I close the problematic table and type
SET, the VIEW window will open. I can re-open the problematic table with
USE, it re-opens with no problem; however, it causes the above problems
again where I can't open the VIEW window and where I get the Error Reading
File message. If I go to another workstation connected to NT terminal
server and open the problematic table while it's open on the other,
problematic workstation, it opens with no problems and no error messages at
all. Thus, the problem seems to be with the workstation connection to NT
Terminal Server and not with the table or it's accessibility on the network.

But I'm stumped. Any help on this is appreciated.