SOLUTION TO ERROR " Your network access was interrupted. To continue close the database and then open it again." __

Ok. This problem is strictly within access. When you walk away from the database for a while it occurs more frequently upon search of record or update of a record. I will have several internet and lan functions running and all work fine without  a hitch or record of the network being interrupted. It existed in XP, win 7 and win 8. Somewhere I read that one guy accidentally discovered that if the file explorer was open to the database location keeping the win system "present" to that connection, his problem disappeared. I have tried this and it greatly alleviates the issue but does not prevent it from occurring. I have tried keeping it open on the server and seems to help in a similar way but unsure.

1. I am solidly convinced it is MS Access having and causing it's own error or how the system services perform on it's behalf.
2. I am convinced that Microsoft is unconvinced it is the fault of Access.
3. Until that changes, since all aspects of the problem reside within Microsoft products only a work around will solve this so I ask this community to work on item 2 and 3!! and report to Microsoft and the community the results of testing.

I have upgraded all LAN hardware items in the path and the problem remains unchanged.

I have more problems on a 32 bit machine than on 64 bit machines (speed).

I am convinced some kind of refresh issue is part of the problem. I have tried some minor changes in the database settings related to refreshing without any noticeable impact.

I suspect memory paging may be related, as when not active in the database it happens and when you first come back and try anything that links back to the server is the ONLY time it happens which would be coincident to paging back into ram.

I haven't had this problem for a number of months now. I no longer leave any explorer windows open and it all works fine. There have been no hardware changes and minimal software changes, but clearly, something has changed because I'm not getting disconnected any more.

One potential change to the database is the addition of an "On Timer" event which may stop this apparent time-out type problem. Perhaps you can try that? I use it to see if a user has been inactive in order to kick them out if they aren't doing anything, but even if I set it to a long duration, I still don't get the error so it might just be the periodical checking that stops the problem.

I solved the issue by creating a copy of the file with the issue (right-click Copy, right-click Paste), tried opening the file and it work perfectly fine.

Once and for all it is not a network problem.. Study as much as I have and you will see it is ACCESS or the way it operates on the network.

This also could be a quota on user space if on a network. I had the same issue with a user who reached their quote. Once increased it allowed my user to open Access again.