[AccessD] Clean Shut Down of Access When Left Open in RDP

[John Colby]

 >>In the interim, I would initiate a timer on the got focus of every 
control on every form that closes all forms and exits the database if a 
certain period of inactivity is reached.

LOL, can you say "class"?

On 8/1/2018 2:35 AM, Bill Benson wrote:
> Why do we always have to "switch" from Access to another platform just to
> get *reasonable* robustness?
>
> This problem is well documented and there no known solution except less
> than perfect mechanisms like Chris Symonds or Alvin Meyer KickThemOff
> solutions, which still are not fool proof, from my viewpoint.
>
> Why doesn't MS implement a fix to a problem that has existed for 10 plus
> years despite many requests for a fix?
>
> Fortunately in my corporate environment, the backend is always SQL Server
> or Sharepoint. A purely Access backend on a multi user platform is just
> asking for trouble.
>
> In the interim, I would initiate a timer on the got focus of every control
> on every form that closes all forms and exits the database if a certain
> period of inactivity is reached. 30 minutes is usually adequate. No message
> to the user, but a scrape of data can be sent to the user in an email
> telling them which form (s) were open, what field data existed at time of
> forced exit, and a request to be more responsibe in future. Don't display a
> "Database will close in XX minutes" messagebox, that will hang the system
> awaiting their response... but you can pop a dialog form on a timer, with a
> label and a cancel button. When the timer on that form reaches its preset
> interval, the form closes and commences database exit routines. If their
> data isn't saved, too bad.
>
> This has to be one of the most frustrating things in all of Access.
>
> On Wed, Aug 1, 2018, 1:01 AM Jim Lawrence <accessd at shaw.ca> wrote:
>
>> Has anyone looked at SSH or SSL connections as they are built into
>> Window10 by default? Extremely robust and resilient.
>>
>> Maybe it might be better to setup remote users on SQL-Express DB BE as it
>> does not require a synchronize connection like a MDB does.
>>
>> Aside: Ran into a similar problem many years ago and moved the entire
>> network's BE to a MSSQL DB and that was an end to corruption issues.
>>
>> Jim
>>
>> ----- Original Message -----
>> From: "David Emerson" <newsgrps at dalyn.co.nz>
>> To: "Access Developers discussion and problem solving" <
>> accessd at databaseadvisors.com>
>> Sent: Tuesday, July 31, 2018 7:24:11 PM
>> Subject: [AccessD] Clean Shut Down of Access When Left Open in RDP
>>
>> Hi Listers,
>>
>>
>>
>> A client has a problem with Access data corruption when a user on RDP
>> leaves
>> the Access application open and the users are forcibly logged off the RDS
>> servers.
>>
>>
>>
>> Is there a way for Access to be closed first before the user is logged off?
>>
>>
>>
>> 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
>>

-- 
John W. Colby