>Or you could just set up a test app that locked a record and started an infinite loop, then kill it through the OS.
>
>>>What I do is first allow the user to log in to SQL Server. Then I do a SELECT that joins the procs table and the syslogins table (both in the master database). In the where clause I look only for processes where the login name is the name of the user who is currently running the application. If I find more than one instance I know that the user is logged in multiple times and I boot the user out.
>>
>>And maybe this could all be done with a Server Trigger ? Geee, I like it ! 8-)
>>What's the sintax to kick off the user ?
>
>I just force the user out of my app. This happens at the front-end, not the server. In my particular case I'm just trying to keep the user from running my app multiple times.

Right, right... A very good idea ! I've scheduled the login tests for the end of this week/beginning of next one, so I'll let you know how things work...

Again, many thanks for your great help !