I have a split database.  FE and Be, each user getting a shortcut to a bat file that copies the latest FE to their computer then opens the database for them.  I am having an issue where some users don't listen (I know) and still try and log in over a VPN or internet into the network and it leaves the lock file in a locked out state that I can not delete, even though I tell them the database will not work well doing this over those connections.  To only log in when on the actual network at the office.  Anyway, how can I determine who the culprit is that keeps leaving the lockfile in a locked state where I cannot delete it.  Yet the users are not logged in anymore.  It is making it difficult to get in and do compact and repair on the BE when needed.  
I do have code in where I can boot a user, but when a user leaves it in that state and they don't actually have it open anymore, that does not work.  It's just that the lock file is not deleting. HELP?