Locked record

[John Esak]

> >    
> Gosh  - now that I think a bit more, I guess the answer to my 
> proposed 
> 'useful' question should be obvious.  Of course filepro has to manage 
> the lockfile in and around the record-locking going on.  So 
> if a record 
> stays locked longer than expected, then of course you would expect 
> everything else to be waiting on it.

Actaully, filePro does not check the rcord locking status of a record when
it backs out of a file... And thereby adjust the the filePro "lockfile" or
not. There is simply, and absolutely NO correlation between record locking
and the filePro lockfile.  For example. You go into clerk, the lockfile says
so... While in clerk you lock record 2. Then you save the record (unlocking
the system lock) and after you do that some other filePro program locks that
record (with a real system record lock). Unaware of this you back out of
your clerk and it releases its increment on the lockfile.  From its point of
view the file is no longer locked, yet that record si still locked by that
other program.  So, your next statement is right. Don't ever try and use the
filePro "lockfile" to track down a "record" lockding issue.

> 
> But trying to resolve the locked record issue by going after the 
> lockfile is definitely not going to help.  Got to find and get the 
> person off the record who is still using the record, or kill 
> process or 
> reboot as previously suggested, but I'll have to try that tool Ken 
> mentioned.
> 
> Bruce
> 
> 
> _______________________________________________
> Filepro-list mailing list
> Filepro-list at lists.celestial.com
> http://mailman.celestial.com/mailman/listinfo/filepro-list
>