[AccessD] Error: Your network access was interrupted

[John Colby]

going to SQL Server back end neatly solves the "WAN incompatibility" issue.


On 11/19/2016 2:48 PM, newsgrps at dalyn.co.nz wrote:
> Further update to this problem from the IT guy:
>   
> "New Switch has been put in and cabling checked, users like Cam have been
> taken off wireless. Av has been modified to remove scanning of DB. I am
> pretty confident at this point that from a networking perspective there is
> no issues here. We have not had any other issues with the system and there
> is other network related task occurring all the time. I think we have a
> compatibility issue with possibly Windows 10 and Access 2016 which is the
> common element here. One of the other guys in the office is Win 7 with
> Office 2016 and he doesn't  have any issues at all. The only difference is
> he doesn't do quoting to the same level as the other two though. I think
> these difference need to be investigated further as it will probably narrow
> down where the issues are."
>   
> Could the Windows 10/Access 2016 combination be a problem (grasping at
> straws).
>   
> Regards
>   
> David
>   
> -----Original Message-----
> From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
> Jim Dettman
> Sent: Friday, 11 November 2016 1:51 a.m.
> To: 'Access Developers discussion and problem solving'
> 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
>    
>    
>

-- 
John W. Colby