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

After recently running into this issue the solution i found was as follows:

After a server crash and subsequent db move to a new server, a cname record had been created for the old server and new share for the db created on a different server.

From this time on Win7 machines were fine accessing the dbase but XP failed with the connection interrupted message.

The clients were actually unable to access the UNC path based on the CNAME record, returning a message of duplicate name found... Turns out that XP and 2008R2 does not fully communicate perfectly without issues.... no surprises with the age difference.

The 2008 Server needed to have a few mods made to allow it to accept incoming connections based on the CNAME record, this fixed the network interruption issues on the XP clients, details here:

http://www.wincert.net/tips/networking/1767-duplicate-name-exists-on-the-network-when-using-dns-alias

So yes in my case it was a communication issue but no it was not an issue with the network itself.... I know its not a fix for everyone here but it might help someone.

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.

I could solve this problem by making a copy of the corrupted database. This copy could be opened normally. However I couldn't erase/overwrite the original one as Windows said it was "open by ACCESS.EXE" (even though Access was closed). Strangely after a few seconds, the original one became de-corrupted and I could open it...

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

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.