DEFINE FIELDGROUP command - Revision history

DCameron: /* Attribute considerations */

2019-02-12T12:52:32Z

Attribute considerations

← Older revision		Revision as of 12:52, 12 February 2019
Line 57:		Line 57:
	A field in a field group cannot have the <var>[[Field_design#Preallocated_fields_.28OCCURS_attribute.29\|OCCURS]]</var> or <var>[[Field_design#VISIBLE_and_INVISIBLE_attributes\|INVISIBLE]]</var> attribute. You can assign any other attributes you choose, paying attention to those that conflict with each other.</p>		A field in a field group cannot have the <var>[[Field_design#Preallocated_fields_.28OCCURS_attribute.29\|OCCURS]]</var> or <var>[[Field_design#VISIBLE_and_INVISIBLE_attributes\|INVISIBLE]]</var> attribute. You can assign any other attributes you choose, paying attention to those that conflict with each other.</p>
	<p>		<p>
	The default attribute for frequency of occurrence for fields in a field group is <var>[[Field_design#Using_the_EXACTLY-ONE_.28EXONE.29_attribute\|EXACTLY-ONE]]</var>, whereas the default for individually defined fields is <var>[[Field_design#AT-MOST-ONE.2C_REPEATABLE.2C_and_EXACTLY-ONE_attributes\|REPEATABLE]]</var>. Of course, you can declare a field inside a field group as <var>REPEATABLE</var>, as well as <var>AT-MOST-ONE</var>. </p>		The default attribute for frequency of occurrence for fields in a field group is <var>[[Field_design#Using_the_EXACTLY-ONE_.28EXONE.29_attribute\|EXACTLY-ONE]]</var>, whereas the default for individually defined fields is <var>[[Field_design#AT-MOST-ONE.2C_REPEATABLE.2C_and_EXACTLY-ONE_attributes\|REPEATABLE]]</var>. Of course, you can declare a field inside a field group as <var>REPEATABLE</var>, as well as <var>[[Field_design#Using_the_AT-MOST-ONE_attribute\|AT-MOST-ONE]]</var>. </p>
	<p>		<p>
	The <var>REPEATABLE</var> and <var>AT-MOST-ONE</var> field attributes have different behavior for fields inside a field group. The <var>REPEATABLE</var> attribute means that the field can have more than one occurrence inside a field group occurrence, whereas the <var>AT-MOST-ONE</var> attribute means that the field can have only a single occurrence inside a field group occurrence. </p>		The <var>REPEATABLE</var> and <var>AT-MOST-ONE</var> field attributes have different behavior for fields inside a field group. The <var>REPEATABLE</var> attribute means that the field can have more than one occurrence inside a field group occurrence, whereas the <var>AT-MOST-ONE</var> attribute means that the field can have only a single occurrence inside a field group occurrence. </p>

DCameron: /* Attribute considerations */

2019-02-12T12:51:30Z

Attribute considerations

← Older revision		Revision as of 12:51, 12 February 2019
Line 57:		Line 57:
	A field in a field group cannot have the <var>[[Field_design#Preallocated_fields_.28OCCURS_attribute.29\|OCCURS]]</var> or <var>[[Field_design#VISIBLE_and_INVISIBLE_attributes\|INVISIBLE]]</var> attribute. You can assign any other attributes you choose, paying attention to those that conflict with each other.</p>		A field in a field group cannot have the <var>[[Field_design#Preallocated_fields_.28OCCURS_attribute.29\|OCCURS]]</var> or <var>[[Field_design#VISIBLE_and_INVISIBLE_attributes\|INVISIBLE]]</var> attribute. You can assign any other attributes you choose, paying attention to those that conflict with each other.</p>
	<p>		<p>
	The default attribute for frequency of occurrence for fields in a field group is <var>[[Field_design#Using_the_EXACTLY-ONE_.28EXONE.29_attribute\|EXACTLY-ONE]]</var>, whereas the default for individually defined fields is <var>REPEATABLE</var>. Of course, you can declare a field inside a field group as <var>REPEATABLE</var>, as well as <var>AT-MOST-ONE</var>. </p>		The default attribute for frequency of occurrence for fields in a field group is <var>[[Field_design#Using_the_EXACTLY-ONE_.28EXONE.29_attribute\|EXACTLY-ONE]]</var>, whereas the default for individually defined fields is <var>[[Field_design#AT-MOST-ONE.2C_REPEATABLE.2C_and_EXACTLY-ONE_attributes\|REPEATABLE]]</var>. Of course, you can declare a field inside a field group as <var>REPEATABLE</var>, as well as <var>AT-MOST-ONE</var>. </p>
	<p>		<p>
	The <var>REPEATABLE</var> and <var>AT-MOST-ONE</var> field attributes have different behavior for fields inside a field group. The <var>REPEATABLE</var> attribute means that the field can have more than one occurrence inside a field group occurrence, whereas the <var>AT-MOST-ONE</var> attribute means that the field can have only a single occurrence inside a field group occurrence. </p>		The <var>REPEATABLE</var> and <var>AT-MOST-ONE</var> field attributes have different behavior for fields inside a field group. The <var>REPEATABLE</var> attribute means that the field can have more than one occurrence inside a field group occurrence, whereas the <var>AT-MOST-ONE</var> attribute means that the field can have only a single occurrence inside a field group occurrence. </p>

DCameron: /* Attribute considerations */

2019-02-12T12:49:53Z

Attribute considerations

← Older revision		Revision as of 12:49, 12 February 2019
Line 57:		Line 57:
	A field in a field group cannot have the <var>[[Field_design#Preallocated_fields_.28OCCURS_attribute.29\|OCCURS]]</var> or <var>[[Field_design#VISIBLE_and_INVISIBLE_attributes\|INVISIBLE]]</var> attribute. You can assign any other attributes you choose, paying attention to those that conflict with each other.</p>		A field in a field group cannot have the <var>[[Field_design#Preallocated_fields_.28OCCURS_attribute.29\|OCCURS]]</var> or <var>[[Field_design#VISIBLE_and_INVISIBLE_attributes\|INVISIBLE]]</var> attribute. You can assign any other attributes you choose, paying attention to those that conflict with each other.</p>
	<p>		<p>
	The default attribute for frequency of occurrence for fields in a field group is <var>EXACTLY-ONE</var>, whereas the default for individually defined fields is <var>REPEATABLE</var>. Of course, you can declare a field inside a field group as <var>REPEATABLE</var>, as well as <var>AT-MOST-ONE</var>. </p>		The default attribute for frequency of occurrence for fields in a field group is <var>[[Field_design#Using_the_EXACTLY-ONE_.28EXONE.29_attribute\|EXACTLY-ONE]]</var>, whereas the default for individually defined fields is <var>REPEATABLE</var>. Of course, you can declare a field inside a field group as <var>REPEATABLE</var>, as well as <var>AT-MOST-ONE</var>. </p>
	<p>		<p>
	The <var>REPEATABLE</var> and <var>AT-MOST-ONE</var> field attributes have different behavior for fields inside a field group. The <var>REPEATABLE</var> attribute means that the field can have more than one occurrence inside a field group occurrence, whereas the <var>AT-MOST-ONE</var> attribute means that the field can have only a single occurrence inside a field group occurrence. </p>		The <var>REPEATABLE</var> and <var>AT-MOST-ONE</var> field attributes have different behavior for fields inside a field group. The <var>REPEATABLE</var> attribute means that the field can have more than one occurrence inside a field group occurrence, whereas the <var>AT-MOST-ONE</var> attribute means that the field can have only a single occurrence inside a field group occurrence. </p>

DCameron: /* Attribute considerations */

2019-02-12T12:48:42Z

Attribute considerations

← Older revision		Revision as of 12:48, 12 February 2019
Line 55:		Line 55:
	===Attribute considerations===		===Attribute considerations===
	<p>		<p>
	A field in a field group cannot have the <var>[[Field_design#Preallocated_fields_.28OCCURS_attribute.29\|OCCURS]]</var> or <var>INVISIBLE</var> attribute. You can assign any other attributes you choose, paying attention to those that conflict with each other.</p>		A field in a field group cannot have the <var>[[Field_design#Preallocated_fields_.28OCCURS_attribute.29\|OCCURS]]</var> or <var>[[Field_design#VISIBLE_and_INVISIBLE_attributes\|INVISIBLE]]</var> attribute. You can assign any other attributes you choose, paying attention to those that conflict with each other.</p>
	<p>		<p>
	The default attribute for frequency of occurrence for fields in a field group is <var>EXACTLY-ONE</var>, whereas the default for individually defined fields is <var>REPEATABLE</var>. Of course, you can declare a field inside a field group as <var>REPEATABLE</var>, as well as <var>AT-MOST-ONE</var>. </p>		The default attribute for frequency of occurrence for fields in a field group is <var>EXACTLY-ONE</var>, whereas the default for individually defined fields is <var>REPEATABLE</var>. Of course, you can declare a field inside a field group as <var>REPEATABLE</var>, as well as <var>AT-MOST-ONE</var>. </p>

DCameron: /* Attribute considerations */

2019-02-12T12:47:28Z

Attribute considerations

← Older revision		Revision as of 12:47, 12 February 2019
Line 55:		Line 55:
	===Attribute considerations===		===Attribute considerations===
	<p>		<p>
	A field in a field group cannot have the <var>OCCURS</var> or <var>INVISIBLE</var> attribute. You can assign any other attributes you choose, paying attention to those that conflict with each other.</p>		A field in a field group cannot have the <var>[[Field_design#Preallocated_fields_.28OCCURS_attribute.29\|OCCURS]]</var> or <var>INVISIBLE</var> attribute. You can assign any other attributes you choose, paying attention to those that conflict with each other.</p>
	<p>		<p>
	The default attribute for frequency of occurrence for fields in a field group is <var>EXACTLY-ONE</var>, whereas the default for individually defined fields is <var>REPEATABLE</var>. Of course, you can declare a field inside a field group as <var>REPEATABLE</var>, as well as <var>AT-MOST-ONE</var>. </p>		The default attribute for frequency of occurrence for fields in a field group is <var>EXACTLY-ONE</var>, whereas the default for individually defined fields is <var>REPEATABLE</var>. Of course, you can declare a field inside a field group as <var>REPEATABLE</var>, as well as <var>AT-MOST-ONE</var>. </p>

DCameron: /* Field considerations */

2019-02-12T12:41:55Z

Field considerations

← Older revision		Revision as of 12:41, 12 February 2019
Line 50:		Line 50:
	The <code>MAKE_MODEL</code> field group must be defined before defining the field(s) and/or field group(s) that belong with it.</p></li>		The <code>MAKE_MODEL</code> field group must be defined before defining the field(s) and/or field group(s) that belong with it.</p></li>

	<li>Once you define a field you cannot move it into or out of a fieldgroup using a <var>REDEFINE</var> command. You must delete the field and relocate it by defining it again, locating it where you want it. </li>		<li>Once you define a field you cannot move it into or out of a fieldgroup using a <var>[[REDEFINE_command\|REDEFINE]]</var> command. You must delete the field and relocate it by defining it again, locating it where you want it. </li>
	</ul>		</ul>

DCameron: /* Summary */

2019-02-12T12:35:55Z

Summary

← Older revision		Revision as of 12:35, 12 February 2019
Line 4:		Line 4:
	<b>Privileges</b>		<b>Privileges</b>
	<p>Any user</p>		<p>Any user</p>
	<b>Function</b><p>To establish the contents of a field group, including the fields and field groups associated with the field group being defined.</p>		<b>Function</b><p>To establish the contents of a [[Field_group_design\|field group]], including the fields and field groups associated with the field group being defined.</p>

	==Syntax==		==Syntax==

ELowell: /* Syntax */

2017-04-06T21:37:16Z

Syntax

← Older revision		Revision as of 21:37, 6 April 2017
Line 18:		Line 18:
	<li><var class="term">OuterGroupName</var> specifies the name of another field group previously defined. The field group being defined is nested under the <var class="term">OuterGroupName</var>.</li>		<li><var class="term">OuterGroupName</var> specifies the name of another field group previously defined. The field group being defined is nested under the <var class="term">OuterGroupName</var>.</li>
	</ul>		</ul>

			<p>For general syntax and usage notes that apply to all forms of the <var>DEFINE</var> command, see <var>[[DEFINE command]]</var>.</p>

	==Adding fieldgroup contents==		==Adding fieldgroup contents==

ELowell at 17:11, 4 April 2017

2017-04-04T17:11:33Z

← Older revision		Revision as of 17:11, 4 April 2017
Line 76:		Line 76:
	</ul>		</ul>

	[[Category: ~~File manager~~ commands]]		[[Category: User commands]]
	[[Category:Commands]]		[[Category:Commands]]

JAL: misc cleanup, section moving, etc.

2015-04-14T20:55:36Z

misc cleanup, section moving, etc.

← Older revision		Revision as of 20:55, 14 April 2015
Line 9:		Line 9:
	<p class="syntax">DEFINE FIELDGROUP <span class="term">FieldGroupName</span>		<p class="syntax">DEFINE FIELDGROUP <span class="term">FieldGroupName</span>
	[WITH FIELDGROUP <span class="term">OuterGroupName</span>]</p>		[WITH FIELDGROUP <span class="term">OuterGroupName</span>]</p>
	<p>Where:</p>		<p>
			Where:</p>
	<ul>		<ul>
	<li><var class="term">FieldGroupName</var> specifies the name of the field group you are defining.</li>		<li><var class="term">FieldGroupName</var> specifies the name of the field group you are defining.
			<p>
			A field group name must be unique among field group names, and it cannot have the same name as any field.</p></li>

	<li><var class="term">OuterGroupName</var> specifies the name of another field group previously defined. The field group being defined is nested under the <var class="term">OuterGroupName</var>.</li>		<li><var class="term">OuterGroupName</var> specifies the name of another field group previously defined. The field group being defined is nested under the <var class="term">OuterGroupName</var>.</li>
	</ul>		</ul>

	<b>~~Example~~</b>		==Adding fieldgroup contents==
	~~<p>To~~ define a field group MAKE_MODEL ~~with~~ fields MAKE and MODEL ~~in it, you would write the following definition.~~</p>		The <var>WITH FIELDGROUP</var> clause identifies a field group that is already defined.
			For example, to define a field group <code>MAKE_MODEL</code> containing fields <code>MAKE</code> and <code>MODEL</code>:
	<p class="code">DEFINE FIELDGROUP MAKE_MODEL		<p class="code">DEFINE FIELDGROUP MAKE_MODEL
	DEFINE FIELD MAKE WITH FIELDGROUP MAKE_MODEL AND ORDERED -		DEFINE FIELD MAKE WITH FIELDGROUP MAKE_MODEL AND ORDERED CHARACTER
	CHARACTER
	DEFINE FIELD MODEL WITH FIELDGROUP MAKE_MODEL		DEFINE FIELD MODEL WITH FIELDGROUP MAKE_MODEL
	</p>		</p>
	<p>~~Example of~~ a field group within a field group:</p>		<p>
			To define a field group within a field group:</p>
	<p class="code">DEFINE FIELDGROUP BIRDS WITH FIELDGROUP VERTEBRATES</p>		<p class="code">DEFINE FIELDGROUP BIRDS WITH FIELDGROUP VERTEBRATES</p>

	<b>~~Usage~~</b>		===Field considerations===
	<p>~~Defining fields after defining~~ the containing field group ~~makes it possible~~ to ~~later~~ add fields to an already defined field group, for example:~~</p>~~		<ul>
			<li>Fields defined in a field group definition follow the syntax rules described in the [[DEFINE FIELD command]].</li>

			<li>Field definitions must follow the definitions of their containing field group. It is then easier to add fields later to an already defined field group, for example:
	<p class="code">DEFINE FIELD YEAR WITH FIELDGROUP MAKE_MODEL		<p class="code">DEFINE FIELD YEAR WITH FIELDGROUP MAKE_MODEL
	</p>		</p> </li>
	<p>The keyword AND on field definitions means that a field group name can contain blanks, just like a field name. ~~You must use the AND keyword to~~ separate ~~the~~ field group name from subsequent attributes:</p>
	<p class="code">DEFINE FIELD COLOR WITH FIELDGROUP MAKE_MODEL AND ORDERED -		<li>The keyword <var>AND</var> on field definitions means that a field group name can contain blanks, just like a field name.
	CHARACTER</p>		<p>
			To separate a field group name from subsequent field attributes, you must use the <var>AND</var> keyword: </p>
			<p class="code">DEFINE FIELD COLOR WITH FIELDGROUP MAKE_MODEL AND ORDERED CHARACTER</p>
			<p>
			The <var>AND</var> is unnecessary if the <var>FIELDGROUP <i>FieldGroupName</i></var> clause is the last field attribute:</p>
			<p class="code">DEFINE FIELD COLOR WITH ORDERED CHARACTER FIELDGROUP MAKE_MODEL</p>
			<p class="note"><b>Note:</b>
			The <code>MAKE_MODEL</code> field group must be defined before defining the field(s) and/or field group(s) that belong with it.</p></li>

	<p>~~The AND is unnecessary, if the FIELDGROUP~~ <var ~~class="term"~~>~~FieldGroupName~~</var> ~~clause is the last field attribute:</p>~~		<li>Once you define a field you cannot move it into or out of a fieldgroup using a <var>REDEFINE</var> command. You must delete the field and relocate it by defining it again, locating it where you want it. </li>
	~~<p class="code">DEFINE FIELD COLOR WITH ORDERED CHARACTER FIELDGROUP -~~		</ul>
	~~MAKE_MODEL</p>~~
	~~<p class="note"><b>Note</b>~~
	~~The MAKE_MODEL field group~~ must ~~be defined before defining~~ the field~~(s)~~ and~~/or field group(s) that belong with~~ it.</p>
	<p>The default attribute for frequency of occurrence for fields in a field group is EXACTLY-ONE, whereas the default for individually defined fields is REPEATABLE. Of course, you can declare a field inside a field group as REPEATABLE, as well as AT-MOST-ONE.</p>

	==~~Usage notes~~==		===Attribute considerations===
	<p>		<p>
	~~The fields defined~~ in a field group ~~definition follow the syntax rules described in~~ the ~~[[DEFINE FIELD command]]~~.</p>		A field in a field group cannot have the <var>OCCURS</var> or <var>INVISIBLE</var> attribute. You can assign any other attributes you choose, paying attention to those that conflict with each other.</p>
	<p>		<p>
	The ~~WITH FIELDGROUP clause identifies~~ a field group ~~that~~ is ~~already~~ defined.</p>		The default attribute for frequency of occurrence for fields in a field group is <var>EXACTLY-ONE</var>, whereas the default for individually defined fields is <var>REPEATABLE</var>. Of course, you can declare a field inside a field group as <var>REPEATABLE</var>, as well as <var>AT-MOST-ONE</var>. </p>
	<p>		<p>
	~~Field group names must be unique among themselves~~ and ~~cannot~~ have ~~the same name as any~~ field.</p>		The <var>REPEATABLE</var> and <var>AT-MOST-ONE</var> field attributes have different behavior for fields inside a field group. The <var>REPEATABLE</var> attribute means that the field can have more than one occurrence inside a field group occurrence, whereas the <var>AT-MOST-ONE</var> attribute means that the field can have only a single occurrence inside a field group occurrence. </p>

	~~Once you define~~ a field ~~you cannot move it into or out of~~ a ~~fieldgroup using~~ a ~~REDEFINE command. You must delete the~~ field ~~and relocate it by defining it again, locating it where you want it~~.

	===Nested field groups===		===Nested field groups===
Line 59:		Line 68:
	DEFINE FIELDGROUP SNAKES WITH FIELDGROUP REPTILES		DEFINE FIELDGROUP SNAKES WITH FIELDGROUP REPTILES
	</p>		</p>

	~~===Attribute considerations===~~
	~~<p>A field in a field group cannot have the OCCURS or INVISIBLE attribute. You can assign any other attributes you choose, paying attention to those that conflict with each other.</p>~~
	<p>The REPEATABLE and AT-MOST-ONE field attribute have different behavior for fields inside a field group. The REPEATABLE attribute means that the field can have more than one occurrence inside a field group occurrence, whereas the AT-MOST-ONE attribute means that the field can have only a single occurrence inside a field group occurrence. The AT-MOST-ONE attribute is the default for fields inside a field group.</p>

	==See also==		==See also==