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

Ok. This problem is strictly within access. When you walk away from the database for a while it occurs more frequently upon search of record or update of a record. I will have several internet and lan functions running and all work fine without  a hitch or record of the network being interrupted. It existed in XP, win 7 and win 8. Somewhere I read that one guy accidentally discovered that if the file explorer was open to the database location keeping the win system "present" to that connection, his problem disappeared. I have tried this and it greatly alleviates the issue but does not prevent it from occurring. I have tried keeping it open on the server and seems to help in a similar way but unsure.

1. I am solidly convinced it is MS Access having and causing it's own error or how the system services perform on it's behalf.
2. I am convinced that Microsoft is unconvinced it is the fault of Access.
3. Until that changes, since all aspects of the problem reside within Microsoft products only a work around will solve this so I ask this community to work on item 2 and 3!! and report to Microsoft and the community the results of testing.

I have upgraded all LAN hardware items in the path and the problem remains unchanged.

I have more problems on a 32 bit machine than on 64 bit machines (speed).

I am convinced some kind of refresh issue is part of the problem. I have tried some minor changes in the database settings related to refreshing without any noticeable impact.

I suspect memory paging may be related, as when not active in the database it happens and when you first come back and try anything that links back to the server is the ONLY time it happens which would be coincident to paging back into ram.

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.

Yesterday I faced this same problem, and I was not able to find anything useful in the Internet. I got it SOLVED! so I write here to share my case and solution:

The reason why I was getting this misleading error message was THE USER running my application: My application is a SERVICE, so user is not the one logged on the computer, but, according to the task manager, user is SYSTEM.

My service is written in Java, and it was trying to connect to a MS Access 2007 .accdb database, getting the error message "Your network access was interrupted. To continue close the database and then open it again".

If I run my service changing "log on as" from "local system account" to "this account" and I enter the user & password used to log on Windows, the problem disappears! As you see, it has nothing to do with closing database and opening it again, and it has nothing to do with network access interruption. An ERROR_ACCESS_DENIED (0x5) would have been much much clearer...  ;-)

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

Does rebooting help?

NO!

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

Regardless of what the error message says, you can also get this error for a database on a local drive. In such instance the error is due to the inability of Access to write to the drive. To remedy the situation, do the following:-

1. Ensure the drive on which the database is situated is not write-protected.
2. Ensure you can create a file and delete in the location where the database is situated.
3. Run Windows disk scanner to remove read/write errors. Read/write errors can occur if your system hangs due to a hardware fault and you had to restart the computer.

Hopes this helps.

Thanks

Bindi Gill

Malaysia