>>Right ? If so, it sounds very easy and good. But suppose that the App crashes for whatever reason :( The lock wouldn't be released, and the user should be forced to reset the machine...
>
>That's the idea. I'm not sure what happens if the application crashes. It may depend on the network OS you're using. I gues there's only one way to find out...

Like a crashtest cmdButton on my form ? ;)
Anyway, I'm talking about Win95 peer-to-peer nets or, better, NT networks.
Let's see...

>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 ?