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

Agree. Had the error and found 'Windows explorer' was causing the error. Checked open files on file server and explorer was open at the database location - closed it and all worked ok. Same as others in that if I copied the database to another name it worked fine - as it would as nobody had this new copy open.

This fixed it for me...

I just had this issue today. Windows 7 client running MS Access 2010 trying to access a shared database that is stored in a network folder that is located on a 2k3 sp2 server on our domain.

I knew it had nothing to do with the network as I had just added the network folder to the client machine and could see the files inside the folder. I could also RDC to the server from the client, and had internet access on the client. This same client computer was on our domain and other users were able to log onto it and had no problems accessing the database, so it was user specific as well.

The fix (I did) to get it to work was in perfect MS form, I right clicked on the file > open with > MS Word... and told it to always open with that program. I then unsuccessfully opened the database with MS Word and proceeded to close Word. I then right clicked on the file again > open with > MS Access... and told it to always open with that program. It opened normally.

Another (side) tip: When I right clicked and selected 'open with', there was nothing in the list besides MS Access. I 'browsed' to ...\program files\MS Office\blah-blah-blah until I found something that was an application I could select (I don't recall the exact name of it). The list then came up with several MS applications for me to chose from.

Hope that helps!

I have a MS Access 2007 database with the backend on a server and the front ends on the laptop or desktop.

Every time I put the screen down of my laptop the connection is disrupted and I have to close the program and re-start it.

Does any one have a solution to this. Perhaps a routine that can be initiated to re-establish the link to the network if the connection has been lost.

I look forward to the genius.

Regards

There is a bug!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

For years the same setup never gave any network interruption errors. The frequency and cascading impact on frequency varies. The bug is in the database. It has been proven by many to be so, yet Microsoft continues to indicate it is the network. I have set my self a rule that has minimized this error's impact and frequency, but nothing yet has eliminated the error. The rule is once I get the network interruption 2 times in one day, all front ends are closed, all back ends are compacted and repaired, then we get back to business. This takes me 20 min to complete and every time I fear loss of data. I have had forms fail with no apparent repair possible and just have to go back and create from scratch. Closing and reopening is all that can be done at a minimumnmmmmm.

You are dead on as to the issue. Did you ever find a solution to this issue?