>>Yes, it's the long-running query in your application that is blocking the
other query from being able to get the snapshot of the locks for your
application's session.<<

That's too bad because it certainly limits the usefulness of accessing ServerSessionLocks table to see if anyone has a table open. I will go back to trying an exclusive lock on the tables instead.

Barry

Barry,

<< That's too bad because it certainly limits the usefulness of accessing
ServerSessionLocks table to see if anyone has a table open. I will go back
to trying an exclusive lock on the tables instead. >>

Yeah, it's something that I'm hoping I can address at some point.  The lock
information is very low-level stuff, and unfortunately there aren't any
lockable objects at that level because they are assumed to be per-session.
So, the only way to synchronize access at this point is through a lock on
the session itself.

Tim Young
Elevate Software
www.elevatesoft.com