>>>No misunderstanding on your part. I ran into the same problem and now avoid the function altogether. Use IF RLOCK() instead. Related to your original question, you stated your need was more for administrative purposes instead of app purposes. What kind of admin are you talking about?
>>
>>Not Admin, troubleshooting. Occasionally, some 'administrative' routines that need to lock the table cannot get a lock. As I have a _LOT_ of code out there operating on the tables in question, I can't figure out which user, (or routine) has which record locked.
>>The only reason I didn't want to use IF RLOCK() then UNLOCK is because of speed. RLOCK() takes about 6 times longer than ISRLOCKED(), but now it doesn't look like I have a choice.
>
>
>If the troubleshooting is not to time consuming have you considered having functionality in your forms to automatically exit the user and disallow rerunning until you are finished?

I wouldn't have a clue as to how to kick a user out of a form from another process. The only session that can unlock a record is the session that locked it in the first place.