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

I get this problem too. As far as I have noticed, it only appears when running Access 2007 on Windows 7 (not on XP for me, and I have tried to replicate it). I have tried changing network ports, cables etc to no avail. In my set-up, I have the database split, with both parts residing on the same server. I have googled extensively for soloutions but yet to find anything useful (although I did fix other access problems - like crashing when you open tables - by uninstalling the HP protect tools which HP install needlessly on new computers).

More than likely you have linked tables in your database. SMB does not let the old share name resolve. Go into link table manager and look how the unc name for the link table is listed. Change the name of unc to the proper name. It could be as simple as you created your links with drive letters instead of the unc name for example  you should use \\servername\share instead of v:\servername\share.

In my case the old \\servername\share was unreachable by my winows 7 laptop but was accessible by my xp laptop due to SMB. The storage administrator had change the name of the servername to a new name and aliased the old name.  I used the new \\newservername\share name when I updated the link. FYI, the linked table manger will prompt you for a path and you can browse to the location, nut it will use a drive letter if you mapped the drive. To use the UNC name just type it in the filename box instead of browsing to it for example \\newservername\share\accessdbname.mdb and click save. Do this for all links or select all and the link table manager will update all links to that unc name(Make sure all links should be updated before selecting all).

The error Network access was interrupted is partially true because MS access could not resolve the unc name.

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.

This is such a nuisance behavior. Searching online doesn’t show any solutions.

Does rebooting help?

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