>>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.

Yes - it is exclusive use of the application. But you only need 160 locks/sec if you're getting 160 hits/sec <s>

As mentioned previously applying the lock seems, in my test, to reduce the maximum number of requests that can be handled by about 15%. If your server is running close to that limit then it may well get backed up anyway. Of course, in real terms, the usual snag applies - short runnning hits will still have to wait while the longer ones complete but overall the server should cope well enough.

I'm not suggesting this is an ideal solution - just that, given the known problem with the VFPOLEDB, it's the best you can achieve....

Regards,
Viv