title: Is it possible to create a deadlock with read-only access?
body: <p>I have a VB6 application accessing a single table on a MSSQL2000 server via ADO. I'm using read-only access (adOpenStatic, adLockReadOnly) There are other applications in the network which do make changes to the table.</p>
  
  <p>For some reason I'm getting errors about my application being chosen as a deadlock victim. </p>
  
  <p>I'm really confused: Why can there be a deadlock when I'm <strong>just reading</strong> from a single table? I'd expect timeouts, because of the writing of the other applications, but not a deadlock...</p>
  
  <p>Can someone shed some light on this?</p>
  
  <p><strong>UPDATE: 2009-06-15</strong> I'm still interested in a solution to this problem. So I'm providing some more information:</p>
  
  <ul>
  <li>It makes no difference if I choose adOpenForwardOnly or adOpenStatic</li>
  <li>It makes no difference if the cursor position is client or server.</li>
  </ul>