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

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

Yes rebooting makes the problem go away (for a while).  Even logging off and back in does.   It is a royal pain.   But it does work.

Hi

I have the same message coming up about 3 times per week, which isn't too damaging to my database, but in every instance I find (if I hadn't saved the current record) that Access 2007 won't let me save the record (so I lose that info/data), but big bully Access forces me to close the database without letting me save that record.  This is extremely irritating.  As is the very misleading heading to this series of posts "Solution to error - [etc]", I read all seven pages and as far as I can make out with my very basic "computerese" there has not been any solution, only a lot of users being mucked about by what must be something within MS Access itself.  I am not part of any network of users, I am the only user in a stand-alone laptop, Win 7.  It IS connected to the wireless modem internet, which is also used by one other user, occasionally at the same time as myself.  This error NEVER USED TO HAPPEN UNTIL QUITE RECENTLY, nothing "visible" has occurred that would explain it simply, EVERYTHING IS UNCHANGED, except (obviously) MS updates to both Win7 and Access2007. 

So this message of mine is (a) to let off steam  (b) to support the conclusions reached by the other guy who SHOUTED  (c) to give my candid assessment of the MS experts' response(s), which is by way of a question   - HOW MANY USERS DOES THERE HAVE TO BE WITH THIS PROBLEM, IN ALL ITS VARIOUS EMINATIONS, BEFORE MS WILL ADMIT THERE IS A PROBLEM?  One million?  Ten million?  regardless of the cause(s) being endlessly debated, and who is or is not right, the bleedingly obvious fact is that many many people are inconvenienced/p-ssed off, and I am just one of them   (d) final thing: can anybody give me an update re whether this thing has, since the latest post date, BEEN FIXED? 

I am going to go out on a limb here and venture the opinion that the answer to (d) is [wait for it, people ....] a big fat "NO.....".

I really identify with whoever it was that said it is almost a case of "bye bye, MS Access and bye bye MS Windows, for good"

Don't you just love the way MS "stuck to their guns" but provided ZERO HELP WITH THIS PROBLEM. 

Talk about the tower of Babel ....

More power to the people, people

(signed) me     (dated) 7th May 2015

Hi

Try the following.

• Create a shortcut to the database in question, by right-clicking on it and selecting "Create Shortcut"
• Edit the shortcut, by Right-Clicking on the Shortcut and selecting "Properties"
• In the "Target" box add the following seperated with a space after the last quotation mark. /decompile
• This would make the target look like this:
• "K:\SOURCING\200 - Data Analysis\Extracts\BW_Extracts.accdb" /decompile
• click apply and run the database from this shortcut.
• Once you have opened the database, run a "Compact and Repair". This is accessed differently dependent on which version of Access you are running. After this you should be able to open the database normally. I have run into this a couple of times, and it is probably down to less than robust network admin, leading to corruption of the file. Hope it helps.

So, halfway to resolving...

The error occurred in the function TablesMatch, which is...

Private Function TablesMatch(strFileName As String) As String

    On Error GoTo ErrorHere

    Dim intFlag As Integer, dbLocal As Database, dbBackEnd As Database

    Dim tdLocal As TableDef, tdBackEnd As TableDef, strReturn As String

    Dim strLocalTableStriped As String

    intFlag = False   ' Initial value, process by exception.

    Set dbLocal = CurrentDb

    Set dbBackEnd = DBEngine(0).OpenDatabase(strFileName)

    Set dbLocal = CurrentDb

    For Each tdLocal In dbLocal.TableDefs   ' Loop through local tables.

        If Len(tdLocal.Connect) > 0 Then    ' This is an attached table.

            For Each tdBackEnd In dbBackEnd.TableDefs    ' Loop thru back-end

                strLocalTableStriped = StripPrefix(tdLocal.SourceTableName)

                strReturn = strLocalTableStriped

                'Debug.Print strLocalTableStriped & " <> " & tdBackEnd.Name

                If strLocalTableStriped = tdBackEnd.Name Then

                    intFlag = True    ' We found a match in back-end.

                    Debug.Print "-- Found it! -- " & tdBackEnd.Name

                    Exit For  ' Jump out for next search.

                End If

            Next

            If intFlag = False Then    ' No match for this attached table.

                TablesMatch = strReturn

                Exit Function

            Else    ' There was a match--continue searching next attachment.

                intFlag = False    ' Reset flag for next table test.

            End If

        End If

    Next

    ' If the function reached here, all tables matched.

    TablesMatch = "OK"

ExitHere:

    Exit Function

ErrorHere:

    Call LogError(Application.CurrentObjectName, "TablesMatch", Err.Number, Err.Description, False)

    Resume ExitHere

End Function

The first time this is called from the function RelinkAccess it reports the first table name rather than the status "OK". So clearly a problem. I removed it from the function RelinkAccess (where it checks if all TablesMatch) and ran the contents of the contents of the IF/THEN/ELSE without confirming that TablesMatch. Everything ran, BUT didn't get all tables. (for my reference it crapped out on T09 WHICH WAS A TABLE THAT HAD BEEN DELETED FROM THE BE, BUT STILL APPEARED IN THE FE). Ran everything a 2nd time AND EVERYHTING WORKED FINE.

So I have been chastised by Microsoft to not shout and to prove it is not the network by getting the same error on a no network setup. Other's smarter than me have proven this. So I am STILL SHOUTING MICROSOFT!

SHOUTING ARE YOU ACTIVE ON RESOLVING THIS ACCESS PROBLEM SOON AS IT HAS GIVEN MILLIONS OF PEOPLE PROBLEMS DAILY AND ENOUGH IS ENOUGH. I WILL CONTINUE TO SHOUT. IT HAS BEEN SINCE WIN7 AND CONTINUES INTO WIN 8.1 AND I BELIEVE HAS A COMPOUND ISSUE SOME RELATED TO THE CHANGES IN NETWORK HANDLING IN WINDOWS AND SOME RELATED TO ACCESS NOT COMPLYING WITH YOUR OWN "IMPROVEMENTS" TO NETWORK ALGORITHMS. 

Maybe if I stop shouting and ask Please, pretty Please?