>Brenda,
>George has a good point about Client 32 - he knows a great deal more than I. However, I DO know that if the network is holding a lock after an app is closed (usually abnormally for this to happen) you cannot release the lock by loading the app again - even if the same user loads it. The lock must be released by the network. Ask your Network Admin. what the default time to release a lock is. He may have it set to 'never'.
>
>>Network is Novell Netware, client 32. I have no network rights. The single application is mine, but the server and network are used by hundreds of other apps. What are my options when this happens?
>>
>>Do you know how RLOCK() are kept? Do you think that if the same person who had the RLOCK() and crashed, then came back through the code that VFP would let them do the RLOCK(). Of course what I really want is for them to RLOCK() successfully, so they will then get to the UNLOCK.
>>
>>Thanks - Brenda

Hello Brenda!

I tested the 32 bit client with Netware 3.11 and found the following:

Opening exclusively a file, and Shut down the clint machine without logoff, the file remain opened, as long as the network release the user. (The timeout is variable by the administrator.) If the same user logon again within the timeout period from the same machine, He/she DOES can open again this file. I get the same result with filelocks and rlocks: the user can lock again thre previously locked and still locked file/record.
(I use this technique to restricts the number of current users. Each user locks a record. For safe recovering, at logon try to logon each record, and leave only one locked.)

BB