Changing Committed FieldMaker Fields

Changing Committed FieldMaker Fields

FieldMaker configurations can be changed after they are committed, even after the new fields are used. A common reason for editing committed fields is to add new values to the Item List of combo-boxes or selection-lists.

Use caution when you make changes to committed fields that are being used in FIMS. Any changes you make could affect existing data in those fields. For example, if you delete a field and commit the change, any data that is currently stored in that field will be lost.

Just as when you create and configure new fields, any changes to the configuration records will only have an effect on FIMS when you run the Commit Changes process. One exception to this rule is any information you change via the Linked Files button on the Screen tab, which determines where the viewer will appear in FIMS. Refer to the Screen Tab for more information.

IMPORTANT: Do not delete the FieldMaker File record unless you intend to remove the entire Plus Page and all of its fields from the database.

If changes are made in error, the database and programs will not be affected until you run Commit Changes, and it is possible to re-create the configuration records. Each time you run Commit Changes, the configuration files data are backed up to the Custom directory, so configuration records matching the current committed FieldMaker setup can be restored.

Field Properties are initially set on the Field tab, from which they are automatically copied to the field Properties when the field is added to the Layout. Some of the Layout defaults depend on the field Configuration passed from the Field set up. But, the Properties on the Layout record control the FieldMaker configuration when changes are committed. If, as is sometimes the case, the field to be changed appears on only one Plus Page (the default, which can be changed on the Screen tab), you can modify the Properties on the Layout tab by right-clicking on the field. The Properties in the Layout configuration record will then be inconsistent with those on the Field configuration record – but there will be no ill effects. If you want to modify the Properties of a field that appears on two different viewers, the best technique for changing them is to delete the field from both Layout records, change the Properties on the Field record, and then re-add the field to both Layouts. That way you can be sure they are consistent.