>I don't know about you Mike, but after thinking about it, and while it is possible, I would not do this at all... I would rather work from the server and manually take care of the tasks needed. You can't guarantee what you may screw up by killing someone's connection.

While I tend to agree with you, there are situations where the business process may call for this. There's no way to speculate what may happen if you killed the connection. It would depend on how the application was written. If all changes are enclosed with a transaction, then there might not be any issues since SQL Server would rollback all uncommitted changes.

-Mike