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

I still have no solution. MS still has not adopted the issue to be Access from my perspective. I now would like to say this:  MICROSOFT, WHEN YOU SPEND THE TIME TO DETERMINE THE CAUSE, IT WILL BE ONE OF YOUR PRODUCTS EFFECTING THOUSANDS OF USER'S AND THERE DAILY LIVES. IT IS IN OUR OPINION ACCESS, IN YOURS ITS THE NETWORK, IN SOME OTHER'S IT'S THE OPERATING SYSTEM. SINCE NO ONE HAS REPORTED ANY ISSUE SIMILAR ON THE NETWORK ITS NOT THE NETWORK. HOW MANY NETWORK CONFIGURATIONS ARE HAVING THE SAME ISSUE? HOW MANY ARE USING YOUR PRODUCTS,,,,,,,,,,,,,,,, AT LEAST AT THE MOMENT!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!

FIX THE DAMN THING, REALLY. ARE YOU DEAF!

Sorry you are upset. Shouting is not going to get this fixed.

Let's try to be rational about it. You claim it's an Access problem; others (and I count myself among them) claim it's a network problem. You don't believe that.

Can we agree on a test? As long as your network is in play the disagreement may continue and you're getting nowhere, so let's take that out of the equation: if you can reproduce the error while all the files are on the local machine, you will have a stronger case to make. Or if you can setup a test at a friend or two's networks and the error continues to appear, you will again have a stronger case to make.

Another way to side-step the issue is to upsize your back-end database to the free Express edition of SQL Server. It "never" corrupts and is not sensitive to network discontinuities.

I have been having this problem for a number of months - ever since we upgraded some of our laptops to Windows 7 and upgraded to Office 2010 as a result. It IS extremely frustrating, especially as there seems to be no answer!  

Our setup uses a shared database back-end over a simple network of around 8 PCs, (wired and wireless). I guess our problem is compounded by having the shared back-end stored on a Linux server - however, this was all fine when we had Windows XP! The problem was quickly identified to be whenever you access the network for something else, e.g. we have shared documents too, Word and Publisher files etc., the Access database link was broken - guaranteed. If you were lucky there was a window of opportunity which could be exploited if you opened and closed the other file quickly enough you could return to the database without the link being broken. Things seemed to have gotten worse recently, hence my post as a result of increased frustration. We always had the same problem and seemingly "random" occasions also, but I had always suspected (and still do) that these are other activities with the network (that I neither know about or understand) that are affecting the link. Especially any period of inactivity was likely to result in this error. Now, however, it can happen every 5 minutes.

I looked at upsizing to the Express version of SQL but it's just not as easy as Access to get the things done that we want to do, that's the beauty of Access I suppose. It's frustrating because it worked beautifully and now it doesn't. It's more tempting (and MUCH cheaper) to go back to XP than to upsize to SQL, but this seems silly. Windows 8 didn't make any improvement either. I'm yet to try Office 2013 or Windows 8.1 but I haven't heard that either of these is a miracle cure.

I'm getting desperate. I believe nobody makes a database better than Access for what we need which puts me in control of the database, but I have looked at what the competition can do and Microsoft will lose my custom if they're not careful and once I'm not using Access I won't need Windows either!

Did you ever find a solution to this issue?

I could not agree with you more. I am close to giving up on Microsoft altogether. It is a shame because Access was a great development tool for a small user base.