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: Oldest
  1. Anonymous
    2016-12-21T14:52:39+00:00

    I don't know how to do that. If you cann't help me, quit it.

    Was this answer helpful?

    0 comments No comments
  2. ScottGem 68,840 Reputation points Volunteer Moderator
    2016-12-21T15:04:14+00:00

    I don't know how to do that. 

    Do what? Click on the Participate link? Just scroll to the top of the page, you will see a link labeled Participate, right under the word Community. Click on it and follow the prompts to post a question.

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2016-12-21T15:42:32+00:00

    Right, same mess. I don't have time to spare. As Divad_S wrote: "Like all thinks MOCOsoft (microsoft), when in doubt reboot.  I am sure glad they don't make AIRCRAFT."

    Forget me.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2017-07-15T18:58:55+00:00

    We discovered a subtle difference for this problem.

    The back-end database was fine. We could open it from another machine without a problem. From the machine with the problem, we found we couldn't open any database on the network.

    Turns out it was a problem with the workgroup security file (MDW) that it was referencing. It had gotten corrupt. Access was being launched with a shortcut that included a /wrkgrp command line parameter that pointed to that MDW file.

    Once we pointed it to another MDW file, it worked fine.

    Was this answer helpful?

    0 comments No comments
  5. Anonymous
    2017-07-18T08:08:34+00:00

    In our case it was relying on group policy preferences GPP map drive configuration.

    The drive from which the database was started was mapped with GPP option "replace".

    This caused msaccess to loose connection when standard group policy event raised.

    Solution was setting option to "update".

    Was this answer helpful?

    9 people found this answer helpful.
    0 comments No comments