Hi Jim.

But wouldn't you say that in an UNbuffered situation, whether RLOCKed or not (after all it is THIS user that has the RLOCK in effect (and can be no other in the code shown because the table is created earlier, so EXCL), that SQL should ALWAYS "see" the record in question?

I am no data expert, but my understanding is that the reason for this is to ensure a repeatable read.

In a multi-user environment, if different users got different results at the same point in time on the same data, it would certainly tend to reduce confidence in the reliablility of the system < s >.