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: Most helpful
  1. Anonymous
    2017-10-03T20:24:47+00:00

    Sounds like a Recordset was left open.  Next time look in Task Manager and see if you spot Access running in the background  If yes, then just exit the process and try again to open your file.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2017-09-14T09:37:58+00:00

    I have this error message, but the database is not open, so I cannot close it. (And I can't open it, which is the problem.)

    Was this answer helpful?

    0 comments No comments
  3. Anonymous
    2017-09-11T19:15:57+00:00

    I don't know if this fact is well known or not but I thought I would share anyway in case it helps someone.

    This applies to an Access backend.

    If you sit at the computer with your backend and you open or close the backend, Access immediately disconnects sleeping computers from the backend by overwriting or deleting the lock file.

    Note that I'm only working with 2 computers but I assume this applies to a multi-computer environment as well.

    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
    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