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

Anonymous
2010-11-02T01:50:09+00:00

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

Microsoft 365 and Office | Access | For home | Windows

Locked Question. This question was migrated from the Microsoft Support Community. You can vote on whether it's helpful, but you can't add comments or replies or follow the question.

0 comments No comments

91 answers

Sort by: Oldest
  1. ScottGem 68,840 Reputation points Volunteer Moderator
    2014-06-04T14:20:11+00:00

    Please don't piggyback your question on another thread. You should start a new question using the Participate link.

    Was this answer helpful?

    0 comments No comments
  2. Anonymous
    2014-06-04T14:21:52+00:00

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

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  3. Anonymous
    2014-06-04T14:25:07+00:00

    Ahh bite me. 

    I experienced the error described in the previous question, and asked the question including my circumstances. luckily I have resolved it, and have posted full information for anyone that follows.

    Was this answer helpful?

    0 comments No comments
  4. Anonymous
    2014-06-21T16:27:55+00:00

    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?

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments
  5. Anonymous
    2014-07-08T12:01:51+00:00

    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.

    Was this answer helpful?

    1 person found this answer helpful.
    0 comments No comments