>>>In your application you can simply store the UserID and Start time when you start and log the time when you exit. You can store this info in a table, then you would have all statistics available to you.
>>
>>That technique does not work 100% of the time. If the workstation crashes, your table will still show the user is logged in.
>
>Good point. I'm sorry, forgot at this moment how we worked around this problem. I guess it's a known problem with known solutions.

As I'm always trying to say, we should collect a set of good techniques and avoid the troublesome ones.

This fellow is using a "loader" / "launcher" to pull a new exe from an ftp server to a server on his LAN. Then he has the users sharing access to this one exe. The loader should be directing the exe to the users' PCs. This will let him update the exe on the server any time he wants. It will let the users finish whatever they are doing and get the update when they are ready and it will reduce network traffic and give the users a performance boost.

Why not gain all of this? Why not suggest this as some kind of best practice? :)