Michel,

Funnily enough, I *tried* to make a response earlier today but my "Send" got an error message. I guess I was a victim!

In any case, we now seem to be learning some *NEW* information . . . there *ARE* two (at least) tables involved! To me this makes a very big difference.

Does your logic lock/update/unlock the 'key' table *before* it does the INSERT INTO?, or do you do the INSERT INTO while the 'key table' is still locked?

If it is *not* the first way above, then it would be a good idea to make it so.

I hope this response gets through (I did not re-type the last, nor will I this one)

Good luck,
Jim N

>>So, you try to lock every 0.1 seconds for 2.5 seconds (probably a little longer). Seems ok. What happens if it cannot lock the record? Did it ever happend?
>
>Not until now, IAC, I need to maximized it again because it is a robot application.