The best way to handle this stituation is with RLOCK(). Issuing record lock on the user's record. Your login table must contain a unique userID of some kind? Find or add the user record then place a lock on that record. If the workstation goes down the record lock will be released automaticly. This works for both Novell and NT networks and provides the simple, reliable way manage who is really using the application. This mechanism along with some creative coding can be used to manage the number of logons per user as well.

>In my app I have a login procedure and everytime someone login I update my login table and this tell me how many users are login and I also have a logout procedure that update the login table, this will work well in a perfect world, where I see a problem is if the users computer shutdown prematurely, if this happen it would not update my login table, so the login count would be off.
>
>I need some ideals on how many users are login to the application.
>
>Thanks Randy