A family of Microsoft relational database management systems designed for ease of use.
I don't know how to do that. If you cann't help me, quit it.
This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
SOLUTION TO ERROR " Your network access was interrupted. To continue close the database and then open it again."
A family of Microsoft relational database management systems designed for ease of use.
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.
I don't know how to do that. If you cann't help me, quit it.
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.
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.
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.
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".