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

Anonymous
2010-11-02T01:50:09+00:00

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

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

91 answers

Sort by: Newest
  1. Anonymous
    2013-10-23T14:20:25+00:00

    Agree. Had the error and found 'Windows explorer' was causing the error. Checked open files on file server and explorer was open at the database location - closed it and all worked ok. Same as others in that if I copied the database to another name it worked fine - as it would as nobody had this new copy open.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2013-10-16T13:38:35+00:00

    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.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2013-09-30T01:55:54+00:00

    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.

    Was this answer helpful?

    4 people found this answer helpful.
    0 comments No comments
  4. Anonymous
    2013-09-23T16:44:36+00:00

    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.

    Was this answer helpful?

    2 people found this answer helpful.
    0 comments No comments
  5. Anonymous
    2013-08-18T22:46:04+00:00

    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.

    Was this answer helpful?

    0 comments No comments