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

Check his network cable and ports.

Hi everyone.

I got this error today for one user.  It used to work ok and now suddenly started to get this error on opening db. If the db file is moved one level up or down in folders - all is fine. Opening backup files with different names from the same location - works. Once the db is replaced with backup and name changed - can't open again.

All other users do not experinece anything similar.  The only solution I found - I created a mirrr db for this particular user.

Just wonderign why it's happening. It seems that the issue is with Access settings. This user while working with db before was the only one who managed to lock it for entry for everyone..... 

Would appreciate any advice.

Thanks,

Olga.

Sorry, but you are incorrect. Event Handling and methods are all handled using conditionals and looping. I'm not sure what you mean by collections and entities in this context. When you come down to it, a computer is nothing more than a bunch of switches that are either on or off. In its purest form a computer program reads those switches, tests whether they are on or off and then does something depending on whether the switch is on or off. 

So I stand by my statement. I will also say VBA has collections, methods and event handling. So again your disdain and thinking that Access is not for serious work shows a lack of understanding of Access..

"But 75% of programming is Conditionals (If...Then...Else and Case statements) and Looping (Do While, For Next, etc.) "

that's where we dont agree, if, then, else, do while, for next lots of children in India/Japan does that, to me, programming is way more than that (collections, methods, event handling, entities, etc).

I cant take serious an app which returns an error message about network issues when you're working standalone.

Nobody on Microsoft can open the code and tell us what's the exception on that try/catch statement?

I hope this reply be more helpful. Thanks

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.