>>>Another approach to this is to use an active flag in your users table. So, instead of checking the lock, when a user logs out or in you toggle the flag. Why? Because you might have some cases where user's can log in more than once.
>>>
>>>>I have a login screen in my vfp app that tests for a record lock before allowing users to login. If this lock fails, it
>>>...snip
>>
>>I do have a logical field that is populated when a user logs in, however, when the application is not exited normally (Crash etc.) the user is still flagged as being logged on. That is why I used the locking technique. In this particular app I cannot allow concurrent logins. The locking works fine now as I was using the isrlocked() function when I should have been using rlock().
>>
>>Thanks for your help!
>>
>>john.
>
>My experience is that a lock on arecord will be released during a crash. My supervisor does not believe me. Can you please direct me to literature on the subject so that I have some proof on the subject...
>
>Thanks in advance.

Asif,
Below I cut out a piece of text from VFP help. press F1 and go to the index and search for LOCK(), scroll down and look for a title called UNLOCKING RECORDS. It is here that you will find the "PROOF ON THE SUBJECT". HTH
John.

*!* ****************Author VFP 5.0 Help
Unlocking Records A table record can be unlocked only by the user who placed the lock. You can release record locks by issuing UNLOCK, closing the table or exiting Visual FoxPro.
*********************