February 19, 1999 - Osmosis Technical Note 3

Subject: Record Locking issues with simultaneous Helix® Client access

When Osmosis is used to enter/modify records AND the collection is accessed by one or more Helix clients, users may experience a condition where Osmosis record entries may appear to fail. When a Helix user opens and selects an entry type view, Helix places a 'write-lock' on that record. If, at the same time, an Osmosis user attempts to modify that record, the modification will be aborted.

A similiar condition exists when a Helix user invokes a POST ALL command.

Osmosis users will receive an error if a locked record is encountered during the ENTRY step. If a write-lock is encountered during a TRANSFER TO step, no error will be reported to the user; the entry will just be skipped. However, the Osmosis log will report an error.

Solutions:

Use the Osmosis log if your scripts include the TRANSFER TO step and check it occasionally for errors.

Employ inert entry forms for Helix users. These type of forms use inert fields to post information to data relations.

If you typically use quick queries on entry type views, try lists or pop-ups to view and/or search for data.

Where posssible, ask users to close entry type views or clear the form so that record data is not left in a 'locked' state.