Save command

[flowersoft at compuserve.com]

> Well, it turns out that 5.0.12DN9 does trigger a freechain rebuild, but it

> does it so fast, I didn't see it unless I set PFBLDFREE=ON.

So now you have a "demonstrable case" that if the freechain message is on
the screen
and you try to add records from another filePro session, that session will
'hang'.
And, if another session is already add record mode before the freechain
message comes on the 
Screen, that session will 'hang' as soon as it tries to save a record and
the
Freechain process will then fail when the user presses the % key, producing
this error message:

*** A System Error Has Occurred ***
/filepro/test/key: Error Number -1
Windows error #33:
The process cannot access the file because another process has locked a
portion
of the file.