[AccessD] Error: Your network access was interrupted

David Emerson newsgrps at dalyn.co.nz
Sat Nov 12 01:43:51 CST 2016


Thanks for your postings Jim.  I have passed them to the IT company.  They
are exchanging a switch to see if this makes any difference.  Will let the
group know our findings.

Regards

David Emerson
Dalyn Software Ltd
Wellington, New Zealand



-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Jim
Lawrence
Sent: Saturday, 12 November 2016 8:20 p.m.
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Error: Your network access was interrupted

Just a note: There are a number of good monitoring programs out there. Some
are free and some are very reasonably priced. 

These applications can be used for managing a network's performance. From
flaky network cards, hubs, routers and switches to data transfer rates from
one computer to another through various programs. If there is any network
congestion a good monitoring system should be able to isolate the problem.

Jim 

----- Original Message -----
From: "Jim Dettman" <jimdettman at verizon.net>
To: "Access Developers discussion and problem solving"
<accessd at databaseadvisors.com>
Sent: Thursday, November 10, 2016 4:51:09 AM
Subject: Re: [AccessD] Error: Your network access was interrupted

The problem with this error is that so many things can cause it, and yes,
it's the network in some way.  JET works fine over a solid LAN with little
issue (and note LAN, not a WAN - can't tell you how many people try to run
it over a WAN, which it was never designed for).   Problem is, JET will
complain loudly long before other apps do, so it usually gets blamed for the
problem.

 Besides the wireless issue (high latency), also look for NIC cards that
have power management (go to sleep) and disable that.  Also disable any
diagnostic protocol they might have (card disconnects from the network, runs
its tests, then re-connects, which will drive JET nuts).

 If your using mapped drives, be aware that windows has a built-in timeout
which needs to be disabled.

 Also have them check that DB's are not being virus scanned on the stations
or servers.

 And unlike the others, I don't believe going unbound is really a solution.
If your going to bother to do that, then you might as well not use Access.
And for most apps it would be a total re-write anyway.  

 A SQL Server backend though to replace JET is certainly an option and
usually not too much of a hill to climb.

Jim.

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
David Emerson
Sent: Wednesday, November 09, 2016 08:31 PM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Error: Your network access was interrupted

Hi Listers,

 

One of my clients is getting the following error:

"The expression After Update you entered as the event property setting
produced the following error: Your network access was interrupted"

 

Does anyone have any experience with this.  Surfing indicates that it is a
network issue rather than an Access one but I am working with another
company in charge of the hardware and am trying to give them leads.

 

Regards

David Emerson
Dalyn Software Ltd
Wellington, New Zealand

 

 

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com

--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com
--
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com




More information about the AccessD mailing list