Jim,

>

>DO WHILE NOT RLOCK() && You'll need more code here to handle the inability to
>                     && lock
>ENDDO
>UNLOCK
>

While not exactly on topic, I am curious about the *strategy* of the additional code mentioned above.

I have seen this handled in different ways like, 'try x number of times, then throw an error, and exit loop.'

What kinds of suggestions do you have for this code? Obviously the answer 'it depends on what the data is to be used for' factors largely, but I was wondering about the in general or most common scenarios.

TIA,
Bill