Typically this is caused by the computer losing its connection. You have checked/replaced all cables, nics, hubs, routers, switches, etc already. As a test, turn off all power saving modes and screen savers (even in cmos) on the workstation completely and make sure none of them kick in to see if it still occurs. Set turn off monitor to never, turn off hard disks to never and system standby to never. Disable hibernation and make sure the cmos is correct for testing also.

]>This seems to be a network problem, but I'm not sure what is causing it. I have an application with 6 users (WinXP Home/Pro clients, Win2K server) and the XP computers are all Dells Dimensions.
>
>The Problem: They will run my application, and leave the PC for a while (10 minutes up to a few hours). When they come back and move the mouse or click on a button, they *sometimes* get Error 1104, "Error reading file", and it doesn't seem to matter which screen they are on.
>
>Error Log: I have an error logging function that saves error info to a table, so if they lost the network connection, it was brief. The status dump usually shows all the tables open, so I'm not sure if they are accessible or not. VFP seems to lose a handle on my main application object and has to be shutdown.
>
>The error happens to 4 of the 6 computers regularly, like 3 or 4 times a day. The other 2 don't seem to be affected by it.
>
>What I've Tried:
>1) Installing an uplink switch/hub for some of them thinking some network cables were problematic (they have had mice chomping on them in the past).
>2) Setting up a temporary Win2K server.
>3) Disabling NAV-CE scanning of "All Files" and just doing "Selected" (this should have been done anyway, but wasn't).
>
>Web searches turn up a common problem with Terminal Server clients, but this company is not using TS for running the app. I've gotten to the point of not charging them anymore until I figure out what it is (or they might hang me for bleeding them dry).
>
>My next test may be setting up another switch with direct cabling instead of going through their patch panel.
>
>Any advice from networking folks out there? I can't imagine this is a VFP problem...