>>I'm not sure of this but I'd hope/assume that the lock is scoped to the thread so it shouldn't be a problem. I'll try to test....
>
>So, this lock should not be seen as exclusive use of the application. I saw it as SET EXCLUSIVE ON in VFP. But, one thing for sure, this is to be avoided. I personally thing it simply doesn't make any sense to have 160 application locks per second.

AFAIR you already handle the errors for the read cases by reading again. So only the insert/update cases need to be watertight - would this not reduce the number of locks needed ?

regards

thomas