You can suspend the timer functionality when necessary - if you do your updates, reports, etc through the same object, make a generic call to set the timer interval to 0, then reset it when you are done.

Also, if this is because of licensing - have you thought about buying a server processor license instead of paying for each seat?

>but what happend is something is going on on the sql server side?, the user coulb be just seat back relaxing waiting for a response from the server
>
>>One concept to check for idleness in an application is to check the MROW() and MCOL() - this will tell you whether the mouse has moved. You can do this with a timer in your application. If it checks every minute or so, and the values have not changed, then the system is likely idle.
>>
>that is not an option, cause they are keeping themselves logged in intentionally, and that is what we want to avoid, because the licenses
>
>>One thing to do also is to put up a box that will inform the user that you are about to exit the application to give them a chance to stop it.
>>
>>
>well, honduras has changed, i don't think there are more doves to hunt, cause, some guys came years ago to hunt them, LOL. but if you come with your son, give me an email if you need a guide or anything
>
>>On a side note - I noticed your location - and it brought back a wonderful memory of when I was 13 years old - going to Honduras to dove hunt with my dad. It was an awesome experience! Maybe one day I can make it back and bring my son!
>>
>>
>>>I need to kick the users out when they've being idle for some period of time, I know this could be simple but don't know how to do it. specially because you have to take in count that we're using sql server and an odbc conneccion to it, so i want to be sure that the sql server is not working on the background making some large query, then i don't want to kick the user out.
>>>
>>>but if it is idle and is not perfoming a sql query in the server, then I want to kcik him out