>>Debugging a client problem. Client keeps getting an "file in use" message. Client is on a network but the only current user. Tracked the message down to a RLOCK() on a table that only has 1 record (holds the next sequential number).
>>
>>1) can abnormal termination keep an RLOCK()

>No, but it may for some network reasons. The best way is just go to the server, open administrative programs and kill all users on this server. It's much faster then starting long discussion with network people.

>>2) can a previous FLOCK() or RLOCK() from the same client prevent an RLOCK(). Can a person lock themselves out?

>It's reasonable to issue UNLOCK (ALL) explicitly after each RLOCK/FLOCK.

Understand that you should unlock after a rlock/flock. But it is a large amount of existing code and I am just trouble shooting. Wondering if client1 does an rlock/flock on a certain record/file, and then later in the same app, can they get an unsuccessful rlock/flock on the same record/file. Can a person have an unsucessful lock because THEY already have it lock?

Brenda