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

While this thread makes for interesting reading it doesn't really help.

We have upgraded the OS and access over the last few years from Access 2002 and Vista, through Access 2007 and windows 7 to the latest Access 2013 and 8.1.

It is only this last upgrade from windows 7 to 8.1 that we are now experiencing this message, therefore I can only surmise the issue is the 8.1 upgrade and how it handles inactive network connections.

However other programs (non MS eg MYOB) don’t seem to have the same network issue and can be inactive for several hours without timing out.

So I have several questions:

1. How do we change the way 8.1 handles inactive connections to leave them open?
2. If non MS programmes can override this and keep the network open are we able to get access to do the same?

I’m not sure if this question is posted in the correct place however I look forward to any help you can supply.

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

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.

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.

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.