>>DO WHILE NOT RLOCK()
>>ENDDO
>>REPLACE CLE WITH CLE+1
>>UNLOCK
>
>Uh, Michel -- I don't think so. :-) This doesn't allow for the fact that you might not be able to get a lock at all -- you'll be hung here forever.

Yes, but for my Visual FoxPro server, I have to wait until it succeed because there is no interface.

I worked well for a year. The only places where I was unable to get the lock was in the INSERT INTO command, where it happened twice in a year, but not in this function.