>>>>Every one in a while Fox stops with the error "Cannot Update Cursor". I select OK and the message "Record is not locked". This is a result from a insert into command. I have set reprocess to 10 and now do not know how to lock a record that has not be created yet. Any help is appreciated.
>>>>
>>>>TIA
>>>
>>>Jeff,
>>>
>>>I had the same problem recently. We're using Novell here. If somebody on the server kill VFP session for some reason (abnormal termination), some file remained locked, and they could be opened only for read, but not write. Re-starting server helps to unlock the file. I would be grateful to hear alternative solutions, because it's usually a pain to determine cause, then restart a server. In Windows Explorer the ReadOnly flag is not set, but the file is locked anyway...
>>
>>Killing users' connections on the server might help. (it might be inappropriate, however, and an overkill :) Also there are sometimes ghost connections.
>
>How can we kill User's connections?

Your network administrator will need to do this, probably from the server console.