freechn

[Kenneth Brody]

On 8/16/2016 9:23 AM, Jose Lerebours via Filepro-list wrote:
> lol - The freechain that appears while user is in IUA mode, in my
> experience, is a hit and miss.  Some times, or should I say often, it will
> get stuck waiting for record to be unlocked, but the locked record is the
> very record it is sitting on ...

I've heard people say they have problems with the "auto-run" freechain (ie: 
when filePro runs it because it detected a freechain error), but I have 
never seen it myself.  I don't know what might cause such problems.

> That said, the fix is really addressing what causes the freechain to
> trigger.  Much has been argued about this over the years and if memory does
> not fail me, these are some of the potential root causes:
>
> a. add/update records via lookup without proper locking in place
> b. changing key fields values within automatic process - never change fixed
> fields in automatic process
[...]

Only creating/deleting records affects the freechain.  Updating existing 
records can't affect the freechain.

A lookup free always locks the record.

The only thing I am aware of (short of O/S or network failure), involves two 
processes looking up the same record at the same time (and at least one of 
them is not a protected lookup), then one of those processes deleting the 
record, followed by the other process writing to that record.

-- 
Kenneth Brody