:: No, the "idea" is that the first to post wins. From your
:: other message, it seems that you think the locking doesn't
:: occur at post time. You argued:

Yes sorry - I had been up for 19 hours and mixed terms. The problem I
reposted in last reply - that the other transactions will continue to select
the same row until its committed - and thus I will have a lot of post
conflicts. That's what Im trying to avoid.

Hmm - Maybe I should try to wrap that post and if it fails, then at that
point get the next row and try that... And so forth.... That might work
well.

:: Definitely don't rely on the exception text to ascertain the

Yes, that's what I really really want to avoid. It's a bad hack.

:: exception. Every DB exception has a distinct 9-digit
:: gdscode. The gdscodes are (kinda loosely) grouped beneath

Thanks. This is what I was hoping for - I'll dig in and hopefully the .NET
provider exposes this as part of the exception class.