This browser is no longer supported.
Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support.
![](data:image/svg+xml, %3Csvg xmlns='http://www.w3.org/2000/svg' height='64' class='font-weight-bold' style='font: 600 30.11764705882353px "SegoeUI", Arial' width='64'%3E%3Ccircle fill='hsl(128, 8%, 22%)' cx='32' cy='32' r='32' /%3E%3Ctext x='50%25' y='55%25' dominant-baseline='middle' text-anchor='middle' fill='%23FFF' %3EA%3C/text%3E%3C/svg%3E)
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 had a broken table link- make sure all your linked tables work- are linked to an available drive/path/
The IT department I consult with reported the same problem as migration to Windows 7 and Office 2010 is underway (from XP and Access 2007). They also use a Citrix server for national support.
The problem is only on Window 7, not on XP.
I sent the SMB 2.0 patch code from MSDN that will also show the same error. They ran that and it did not change anything.
this is a subscription site. I have yet to get an account. But, they claim to have tried seveal things with out success (listed at this link).
Just a note: Upgraded Access 2000 to Access 2007. Front end - linked to back end. No problems with this for last year, until Windows 7 - Office 2010 roll out. Had tested compatibility on a stand-alone workstation of Wondows 7 / Office 2010 (C: / drive) to validate code, DLL, and Excel reporting automation. No problems found.
As an aside for anyone else getting this problem and loosing vba code as a result, it is possable to export your vb modules after you have had the error and re-import them after re-opening to avoid loosing anything.
I replaced my links which were using mapped drives with the full network paths (using the linked table manager - pretty quick and easy) and all references to mapped drives in my VB code, then disconnected my mapped drives (to ensure i hadn't missed any references) and re-opened the database (via the full network path).
Unfortunately it didn't make any difference - after a few hours (and many unsaved vba changes) I got the usual network access interrupted error.
I avoid using mapped drives and use the UNC path instead.
To use unc paths, when manually relinking, instead of using windows explorer to find the path to the backend, instead go to the network folder on the computer and navigate to the backend from there.
The path will look something like \\Servertree\Folder name\ Backend name