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

Just confirming that after deleting the table that existed in the FE (as a linked table) but not in the BE, FROM the FE - Everything worked fine.

Probably not going to help many people, but does show it's not just a network issue...

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.

We have the same error, and only on Win 7 pcs with Office 2010 , all Win XP pcs with Office 2003 in the same location never have the issue. I have tested the network running a constant test and it never drops, but still get the same error as everyone else. So I think its pretty safe to say its not a network fault its something else.

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!

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.

As an aside for anyone else getting this problem and loosing vba code as a result, it is possable to export your vb modules after you have had the error and re-import them after re-opening to avoid loosing anything.