>Good sugggestions. But why does a SELECT have anything at all to do with a deadlock?

It's all about the locking. When SQL Server reads a resource (ex. row in a table) it puts a Shared lock on the resource. SQL Server also puts Intent locks higher up the hierarchy. For example, SQL Server would put a shared lock on the row and an Intent Shared (IS) lock on the page and on the table.

The Trace flag that I gave your earlier will dump the connections and resources that participated in the deadlock. It will tell you the tables that were involved. That should help track things back.

-Mike