|Uses of Inert Fieds|
Inert fields do not store data — they hold the entered value until you close the view or go to the next record. There are many users for inert. Some of them are described below:
Inert fields are often used on Host forms to enter query criteria such as date ranges or record number.
Inert fields may be used to temporarily hold values that are being posted somewhere else for permanent storage. For example, ifyou wish to post information from one Relation into another, but you do not want to store the information in the Source Relation, create an inert field and place it on the entry form in the Source Relation. Post this inert field to the Target Relation. To avoid posting an undefined value, if you happen to leave the inert field empty, place a "Lookup" abacus to display the current value of the Target field in the same data rectangle as the inert field on the template.
Inert fields may be used to avoid recursive posts. Helix will not permit you to use the Target field, which you want to modify, in the calculations which you are using to modify the Target field. To avoid this recursion, you should post the calculation into an inert field with an Option 0 (zero) post, then post the inert field to the Target field with an Option1 or Option 2 post.
Inert fields may be used to delete information in a field. Since an inert field is undefined unless you enter or post information into it, you can post an empty inert field into a stored field to replace the stored value with an undefined value.
Inert fields may be used to validate other fields on a form. Unlike regular field validation, which is record specific, inert field validation is form specific. This means you can place a validated inert field on a form and the validation will only occur on that form.