We have a sage 200 add-on which can be run as a windows task which clears sage 200 user disconnected logins

I think arbitrarily clearing disconnections without understanding why they are occurring if a bad idea as it could mask either a network issue, server issue or a lack of understanding from the users - i.e. it would be a bad idea to use task manager  to kill a Sage 200 session whilst its despatching sales orders that are traceable. That said  there can be a considerable number of disconnected login's recorded if you are using Sage CRM that is integrated.

I think that better, more specifically easier to access and understand, logging is required to indicate the cause of record locks, rather than keeping the locks present.

I observe that many disconnected logins are associated with network failures to maintain contact, and/or users switching off their PC without properly logging out of Sage.  The record lock/s that are left behind are frequently an indication of what the user was trying to do at the time of disconnection - and partially-updated records can cause considerable problems.  Whilst I recognise that if the user wasn't doing anything (e.g. just had a menu open) then no locks are relevant - but if the user was part-way through entering a new sales or purchase order then you are likely to end up with corrupt sales orders (starting with ###) and stock allocated to that corruption.  Sage removed the ability to see what the user was doing at the time of disconnection - and so we lost the ability to forecast data corruption.

I have to vote against your idea.

i agree!