>>The only issue we have with this method is that we are reliant on the user logging out and not all users seem to be able to remember to do that and strand their login record which requires a clean up method.
>
>One way around this is the activity timer, which checks the last recorded activity timestamp (in the login record) against the one in the app itself (which is refreshed from any set of events - any .gotFocus(), .click(), .activate() and select other methods). If the current app timer is a certain time beyond the time in the record, the app concludes that the user is gone, saves any changes, logs him out automatically and shuts down. If not, it updates the time in the login table, i.e. refreshes the record of the user's presence.
>
>Now the intervals involved may be a matter of trial and error... the app timer may fire perhaps every minute or ten, and the allowable inactivity interval may be between 20 and 120 minutes. The latter may be a setting that may change from client to client.

As every time with timers: They are not reliable long term (i.e. long interval). We had a thread about timers not firing in the last weeks?