[AccessD] Idle Access seems to drop connection

John W. Clark John.Clark at niagaracounty.com
Thu Oct 19 16:16:26 CDT 2017


First, if you haven't done so already, I'd try copying a front end from a "working" device. Perhaps "something" got messed up with their FE.

Next, speaking as someone who has in-house networking people (and sometimes is one) their always going to say that. Unless something sticks right out it is never the network's fault.

Now, having said that, I'm thinking it is more likely PC end...network but PC end maybe. Make sure all updates are done. Start comparing PC settings...it is like a needle in a haystack.

It sounds like it is "looking" for something
Can you get the system monitor up and watch utilization while running the program?

Honestly, we run into stuff like this...not frequent, but not rarely either, and whenever we can we'll recover to an earlier date, or even wipe the machine and start from scratch. It can take time but so can finding that needle.

Sent from mobile device


________________________________
From: AccessD <accessd-bounces at databaseadvisors.com> on behalf of David Emerson <newsgrps at dalyn.co.nz>
Sent: Thursday, October 19, 2017 4:45:56 PM
To: 'Access Developers discussion and problem solving'
Subject: [AccessD] Idle Access seems to drop connection

Hi Team,



I have a client that has several users with FE's connected to the same BE.
All of them seem to work fine except for 1 user.



When this user starts his copy there is a 30 second delay while the
programme opens (it gets data to display a report).  Then when the orders
screen is open via a command button it opens relatively quickly (within a
couple of seconds).



However, if he leaves the system for 5 minutes or so then the next time he
does something that requires getting data (for example closing and opening
the orders screen) there is a 30 delay again.  After the initial delay the
system works fast again.  If he immediately closes and opens the orders
screen without a delay between tasks then it opens immediately without a
delay.



I know there is a timeout setting for SQL connections but this is purely an
Access BE.



The IT company has checked the network (it is a wired network) and all seems
to be fine.  The user has another similar database (although smaller in data
size) and it doesn't have the same problem.



Any thoughts on what may be causing the delay?



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


Notice: This electronic transmission is intended for the sole use of the individual or entity to which it is addressed and may contain confidential, privileged or otherwise legally protected information. If you are not the intended recipient, or if you believe you are not the intended recipient, you are hereby notified that any use, disclosure, copying, distribution, or the taking of any action in reliance on the contents of this information, is strictly prohibited. Niagara County is not responsible for the content of any external hyperlink referenced in this email or any email. IF YOU HAVE RECEIVED THIS TRANSMISSION IN ERROR, PLEASE NOTIFY THE SENDER IMMEDIATELY BY EMAIL AND DELETE THE ORIGINAL MESSAGE ALONG WITH ANY PAPER OR ELECTRONIC COPIES. Thank you for your cooperation.


More information about the AccessD mailing list