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

I can re-create this error on my local machine, using only a single Access file with local tables. I am running Access 2013, on Windows 7 Enterprise 64-bit with SP1. I have two local tables, about 25,000 records each. I am opening table 1 and using a keyfield from that to select one record from the second table. My code looks like this:

While Not NewData.EOF

    i = i + 1

    Forms![frmStatus]![lblProcess].Caption = "Processing " & i & " of " & NewData.RecordCount & ": " & NewData![LPE ID]

    DoEvents

    SQLstr = "SELECT * FROM [Control Master] WHERE (([MasterIndex])=" & NewData![MasterIndex] & ");"

    Set Archive = db.OpenRecordset(SQLstr)

    If NewData![Sales Order No] <> Archive![Sales Order No] Then

        Set Archive = Nothing

        SQLstr = "UPDATE [Control Master] SET [Sales Order No]='" & NewData![Sales Order No] & "' " _

            & "WHERE (([MasterIndex])=" & NewData![MasterIndex] & ");"

        DoCmd.RunSQL SQLstr

        SQLstr = "INSERT INTO [ChangeList] ( [CPEID], [Sales Order], [Product Code] ) " _

            & "VALUES ( '" & NewData![LPE ID] & "', '" & NewData![Sales Order No] & "', '" _

            & NewData![Part Code] & "' );"

        DoCmd.RunSQL SQLstr

    End If

    NewData.MoveNext

Wend

After about 1000 records, it fails on the OpenRecordset statement with "Your network access was interrupted..." I have tried it both with and without the status form telling me how many records have been processed. It never fails on the same record. This is a very basic loop and very basic table update. I cannot see how there is anything from the network that would cause this error.

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.

I replaced my links which were using mapped drives with the full network paths (using the linked table manager - pretty quick and easy) and all references to mapped drives in my VB code, then disconnected my mapped drives (to ensure i hadn't missed any references) and re-opened the database (via the full network path).

Unfortunately it didn't make any difference - after a few hours (and many unsaved vba changes) I got the usual network access interrupted error.

You also need to be careful using a flash drive in this manner. I've seen beaucoup reports over the past few years about data corruption in Access when using a flash drive in this manner. Apparently many flash drives report that data transfer is complete when, in fact, it isn't quite, and disconnecting before the transfer is complete is apt to cause corruption.

Linq ;0)>

There's always more than one way to skin a cat!

Jeanette,

I was recently working with a client and their IT department decided to move the backend database to another server. They did it without notifying us and, although we didn't get the message the OP got, it did have the unfortunate effect of corrupting the backend. I had a "fun time" getting it repaired.

Lynn Trapp MCP, MOS, MCAS