[AccessD] Error: Your network access was interrupted

Wed Nov 30 07:52:43 CST 2016

<<What is odd is these units (and users) are all similarly specced - using
the same tools and skills.>>

  A recent trend in the office suite and with software in general is that
the runtime environment is becoming increasingly complex.

  Just look at the recent problem with network interruptions that we were
discussing; something as innocuous as a group policy with "Replace" instead
of "Update" causes a problem.   Or the move to Win 7 when a lot of Access
apps failed, only to realize that Microsoft added a timeout on mapped drives
of ten minutes (and that's not just Access - had a client with UPS's World
Ship software where that caused a problem).

  And with Office specifically, you now have the MSI/Installed version vs
Click to Run/Office 365 builds. That seems like it will become more of a
hassle as time goes on as I'm seeing more and more questions/problems
related to the mixing of the two.

 I'm not so sure it's the products themselves that are the problem, but the
environment that they run in.

Jim.

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
Darryl Collins
Sent: Tuesday, November 29, 2016 05:43 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Error: Your network access was interrupted

"I don't have anyone running Access 2016 on Windows 10 but I do seem to have
a more support issues with Excel 2016  crashing/locking, etc. on Windows 10
than on Windows 7. So it is possible."

We run Access 2016 under windows 10 and it has been the best and most stable
version of Access I have used to date.  Surprisingly so, as traditionally MS
Access was the unloved basket case of the Office suite.  However - I totally
agree with your Excel 2016 observation.  Excel 2016 is less stable and more
bothersome than XL2010 - although just how bothersome seems to vary between
PC's.  On some units it is fairly stable (although still troublesome) and on
others it crashes with alarming regularity.  What is odd is these units (and
users) are all similarly specced - using the same tools and skills.

I suspect some of the issues is due to the change to how the UI is handled -
especially if you are using code to do things (I also suspect that they
didn't beta test the VBA side of thing much either).

On the upside, at least updates are regularly pushed out - often with bug
fixes.

Cheers
Darryl.

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
David Emerson
Sent: Wednesday, 30 November 2016 7:55 AM
To: 'Access Developers discussion and problem solving'
<accessd at databaseadvisors.com>
Subject: Re: [AccessD] Error: Your network access was interrupted

Hi team,

The IT guy says that it seems to have been caused by the way mapped drives
were being refreshed by a group policy.  The setting was Replace when it
should have been Update.

Problem solved and not Access's fault :)

Regards

David Emerson
Dalyn Software Ltd
Wellington, New Zealand

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
John R Bartow
Sent: Tuesday, 22 November 2016 5:40 a.m.
To: 'Access Developers discussion and problem solving'
Subject: Re: [AccessD] Error: Your network access was interrupted
Importance: High

I don't have anyone running Access 2016 on Windows 10 but I do seem to have
a more support issues with Excel 2016  crashing/locking, etc. on Windows 10
than on Windows 7. So it is possible.

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of
newsgrps at dalyn.co.nz
Sent: Saturday, November 19, 2016 1:48 PM
To: Access Developers discussion and problem solving
Subject: Re: [AccessD] Error: Your network access was interrupted

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

--
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

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