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

The best solution I have found so far is to omit any DNS names, and full UNC addresses, in my mapped network drive for the BE database file. When linking to tables in the BE file, I tried creating links to the BE in different ways:

1. first mapped a network drive using the UNC address like \\servername\sharename\accessfilename.mdb. This worked with no problem in Access 2003, but I started seeing the error messages sometime after we upgrade.
2. I have also tried creating the table links in Access with direct UNC addresses and bypassing the use of a map network drive.

These options did not solve the problem for me.

Now I map a network drive using the actual IP address of the target server where the BE files reside. Yes, I know there are disadvantages to this, but as a result the Network Disconnect errors have disappeared except for rare occurrences.

Whether this is a problem specific to Access, or to the network, can be debated ad infinitum. Why can I work in Excel VBA using my old way of mapped network drives and have no problems with network disconnects? Probably because I am not filling memory buffers from Excel like I would get from Access. Is there something going on with DNS or ARP that is too unstable or unreliable for Access? Why does removing DNS from the network link make it work? I don't know.

This may not work for everyone. Just putting this out there as a working solution, in case it helps anyone else.

Tim,

The fact that FE and BE reside on the same server does not change the network issue. The fact of the matter is that processing is done on the local machines. Therefore, data packets are moving between the local PC and the servers. These data packets can be sensitive to glitches in that traffic that would not affect other programs. 

By the way, running the FE from the server is not recommended. FES should be installed locally and not shared. Doing so will limit the amount of network traffic.

go learn some programming and nevermind ms access. You cant take it to serious work. Period.

The sad is MS doesnt assumes that and doesnt solve it as well.

Depends on what you define as "serious work". Frankly I think that's a typical IT attitude that shows a lack of understanding of what Access is and can do. I use it for some VERY serious work. My company has over 100 Access apps, many of which are integral to our business. 

Also VBA IS Programming. It is every bit as much programming as VB or C#. VBA makes programming a bit easier because it does many things for you. For example, it takes about 9 lines of code to create a combobox in a vb.Net app and no coding in Access. But 75% of programming is Conditionals (If...Then...Else and Case statements) and Looping (Do While, For Next, etc.) And VBA allows you do a lot of that. 

Sorry Mr Lima, but rather than be helpful your comment just displays your ignorance.

go learn some programming and nevermind ms access. You cant take it to serious work. Period.

The sad is MS doesnt assumes that and doesnt solve it as well.

I started reading this string in hopes or resolving our "network access interrupted" error.

We are running an Access 2013(32bit) front end attached to a back end on the same drive, in a hyper-v Server 2012r2 terminal server environment.  I am not a network expert but it seems to me that since both the fe and be live on the same drive on the local server there should be no network errors.

Sometimes this error occurs while users are doing data entry and at other times when they are not touching their keyboards or mice.

I am unsure if this is an Access 2013 or Server 2012r2 issue but sure would appreciate any assistance in resolving it.

Thanks,

Tim Reid