Skip to content Skip to sidebar Skip to footer

Access Your Network Access Was Interrupted To Continue Close the Database and Then Open It Again

Ask your network guys to check those users' connection to make sure it really isn't a network issue although all the network guys I know blame everything on Access.

Your database is split, right? It should be...with the tables on the network and a local copy of the front end on the users' hard drive?

Bill Mosca
ThatllDoIT.com

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

To go with what Bill said - it could be a bad NIC (Network Interface Card) in them (they do go bad sometimes) so they should be tested as well.

And as Bill has said, the network guys sometimes need prodding because they can't admit that their network might have issues so they blame it on Access.  But Access will not usually give you that error unless there was a dropped connection.

But, a BIG IMPORTANT THING TO NOTE:  This database NEEDS to be split (if it isn't already) and a copy of the frontend on each user's machine (if it isn't already).  If that isn't set up that way then when you do get those network disruptions (no matter how brief) and someone is in the database, then you can pretty much count on corruption occurring and if you didn't have it split, then the entire thing would be hosed and you might lose all of your data.  If it is split but you are running a shared frontend, then the frontend will likely get hosed and then everyone can't work.  But if you have copies on each user's machine not only is it less likely that corruption will occur but it will probably mean that one person may be down but everyone else can keep on working while you go and give the one user, who has a corrupted frontend, a new file.

Just some things to note.

-----
Microsoft Access MVP 2008, 2009, 2011
If a post was helpful click the FOUND THIS HELPFUL link

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Thank you very much for the quick responses:

but...
Per boblarson:
actually, this is a pier-to-pier system with Network Access Devices (RAID drives) holding the back-end of the database and the local work stations holding the front end.

This network in its present configuration has been up for about 5 years.  As workstations aged they were replaced with newer versions of Windows and MS Access.

The three (of ten) workstations that are currently having errors are using Access 2007 and Access 2010.

We have no 'network guys'.   It's all on us.

Is it coincidence that 3 users started having this problem within the space of a week or 2, when no one had the problem in 5 years?  It makes me question the bad NIC idea.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

So, you might want to test your router.  It might be having issues.  In a peer to peer network your router/switch is still going to be a particular vulnerable spot.  I have seen several routers or switches go bad and that could be causing your drops on 3 of the 5 computers.

-----
Microsoft Access MVP 2008, 2009, 2011
If a post was helpful click the FOUND THIS HELPFUL link

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Guess what!!
One of the workstations using MS Access 2003 just got the following message:

"Run Time Error

Disk or Network Error"

Is this the 2003 version of the message gotten by the Access 2007 systems that started this thread?

Thanks, boblarson, for your insight.  We will be looking at the router.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Yup, that's the same error, just different wording.

Bill Mosca
ThatllDoIT.com

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

This thread has either been duplicated or trimmed. Various efforts beyond what is here have been made by users and others and it was determined without a doubt to be An Access error, not a network error.

When Microsoft believes this, then it might get fixed. Till then all I can do are the things others fell help resolve or are a work around. Hundreds of people are complaining about this and we can't all have no other network symptoms and have it be the network.

So I will search for such fixes and try them. I will monitor this thread emails sent and see if a similar thread can be identified.

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

This thread has either been duplicated or trimmed. Various efforts beyond what is here have been made by users and others and it was determined without a doubt to be An Access error, not a network error.

When Microsoft believes this, then it might get fixed. Till then all I can do are the things others fell help resolve or are a work around. Hundreds of people are complaining about this and we can't all have no other network symptoms and have it be the network.

So I will search for such fixes and try them. I will monitor this thread emails sent and see if a similar thread can be identified.

I just started getting the same error on a standalone laptop. Could it be because the database is to large?

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

Please don't piggyback your question on someone else's thread. Please use the Participate link above to start your own thread. You can include a link to the older thread.

Size of the database rarely is an issue. The real issue is Access is very sensitive to dropped connections.

Hope this helps,
Scott<>
Blog: http://scottgem.wordpress.com
Microsoft Access MVP since 2007

Was this reply helpful?

Sorry this didn't help.

Great! Thanks for your feedback.

How satisfied are you with this reply?

Thanks for your feedback, it helps us improve the site.

How satisfied are you with this reply?

Thanks for your feedback.

vallehaudeare.blogspot.com

Source: https://answers.microsoft.com/en-us/msoffice/forum/all/your-network-access-was-interrupted-to-continue/c61b2e9d-4972-e011-8dfc-68b599b31bf5

Post a Comment for "Access Your Network Access Was Interrupted To Continue Close the Database and Then Open It Again"