[AccessD] Idle Access seems to drop connection

[James Button]

To actually try identifying the cause 
I'd start by running resource monitor and checking if there is actual activity
happening during those 30 seconds

If little activity - the it may well be that the comms link is being baulky - or
maybe even trying to go wireless??
Then again - you may see massive paging 
or downloads 
or Just note the drive light going with no activity being reported by task
manager - that could point to pagefile expansion

Then again just not getting the problem may be an acceptable result!

JimB

-----Original Message-----
From: AccessD [mailto:accessd-bounces at databaseadvisors.com] On Behalf Of Arthur
Fuller
Sent: Thursday, October 19, 2017 10:24 PM
To: Access Developers discussion and problem solving
<accessd at databaseadvisors.com>
Subject: Re: [AccessD] Idle Access seems to drop connection

There have been threads on this. If you declare a public variable and open
a recordset witb it you won't lose your connection.

On Oct 19, 2017 4:47 PM, "David Emerson" <newsgrps at dalyn.co.nz> wrote:

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
-- 
AccessD mailing list
AccessD at databaseadvisors.com
http://databaseadvisors.com/mailman/listinfo/accessd
Website: http://www.databaseadvisors.com