Jim,

>1) The table of "Commands that Automatically Lock Records and Tables" should mention...
>--- that tables opened after SET EXCLUSIVE ON is in effect will cause a lock of the table(s);
>--- that tables opened with the "EXCLUSIVE" clause of the USE command cause a lock of the table.

I would disagree with this as EXCLIUSIVE use is NOT the same as a File Lock. I don't believe that exclusive use secures a file lock.

>3) The table under the "Unlocking Data" section lists "SET MULTILOCKS OFF" and describes its effect as "Enables automatic release of the current lock as a new lock is secured" and the Command Reference for SET MULTILOCKS states "Switching SET MULTILOCKS from ON to OFF or from OFF to ON implicitly issues UNLOCK ALL — all record locks in all work areas are released.". I see a contradiction between the two entries. In fact I can't really understand what the first quotation is actually telling me.

This one is pretty clear to me, SET MULTILOCKS OFF sets up a situation where securing a record lock automatically relaeses any other record lock that may have been in place on the table. Also flipping the value of SET MULTILOCKS will release all record locks that are in place at the time the value is flipped.

For example if I have three record locks in place and I then SET MULTILOCKS OFF the three locsk will be released. If I have a record locked and I SET MULTILOCKS ON that record lock will be released.