Field names - Revision history

DmeWiccan: Automatically generated page update

2014-05-09T22:45:43Z

Automatically generated page update

← Older revision		Revision as of 22:45, 9 May 2014
Line 184:		Line 184:
	</p>		</p>

	[[Category:~~File management~~]]		[[Category:Model 204 files]]

JAL at 22:47, 31 January 2014

2014-01-31T22:47:52Z

Show changes

ELowell: ELowell moved page Field Names to Field names

2013-12-12T21:13:59Z

ELowell moved page Field Names to Field names

← Older revision	Revision as of 21:13, 12 December 2013
(No difference)

ELowell: /* Reserved words requiring special attention in names */

2013-05-23T15:54:03Z

Reserved words requiring special attention in names

← Older revision		Revision as of 15:54, 23 May 2013
Line 154:		Line 154:
	<p class="code">DELETE PROC '%SAVINGS'		<p class="code">DELETE PROC '%SAVINGS'
	</p>		</p>
	~~[[Category:File manager]]~~
	[[Category:File management]]		[[Category:File management]]

Rob at 03:52, 25 April 2013

2013-04-25T03:52:59Z

← Older revision		Revision as of 03:52, 25 April 2013
Line 156:		Line 156:
	[[Category:File manager]]		[[Category:File manager]]
	[[Category:File management]]		[[Category:File management]]
	~~[[Category:File architecture and management]]~~

DmeWiccan: Automatically generated page update

2013-04-19T13:09:55Z

Automatically generated page update

← Older revision		Revision as of 13:09, 19 April 2013
Line 156:		Line 156:
	[[Category:File manager]]		[[Category:File manager]]
	[[Category:File management]]		[[Category:File management]]
	[[Category:File ~~Architecture~~ and ~~Management~~]]		[[Category:File architecture and management]]

DmeWiccan: Automatically generated page update

2013-04-18T14:12:25Z

Automatically generated page update

← Older revision		Revision as of 14:12, 18 April 2013
Line 155:		Line 155:
	</p>		</p>
	[[Category:File manager]]		[[Category:File manager]]
	[[Category:File ~~Management~~]]		[[Category:File management]]
	[[Category:File Architecture and Management]]		[[Category:File Architecture and Management]]

Rob: /* Field name rules */

2013-04-17T23:44:16Z

Field name rules

← Older revision		Revision as of 23:44, 17 April 2013
Line 1:		Line 1:
	==Field ~~name~~ rules==		==Field and Fieldgroup naming rules==
	<p>Every field in a <var class="product">Model 204</var> file has a ~~field~~ name by which it is referenced. The following restrictions apply to ~~field~~ names:</p>		<p>Every field and fieldgroup in a <var class="product">Model 204</var> file has a name by which it is referenced. The following restrictions apply to these names names:</p>

			<p>Note that a name can only be used once per file (a fieldgroup and field can not have the same name).</p>
	<ul>		<ul>
	<li>~~Field names~~ must begin with a letter.</li>		<li>Names must begin with a letter.</li>
	<li>When more than one consecutive space appears in a ~~field~~ name, the extra spaces are ignored.</li>		<li>When more than one consecutive space appears in a name, the extra spaces are ignored.</li>
	<li>~~Field names can~~ contain as many as 255 characters. ~~Field names~~ should be short enough to enter easily, but long enough to have meaning.</li>		<li>Names may contain as many as 255 characters. Names should be short enough to enter easily, but long enough to have meaning.</li>
	<li>Certain restricted words and special characters either cannot be used at all or can be used only with special syntax.</li>		<li>Certain restricted words and special characters either cannot be used at all or can be used only with special syntax.</li>
	</ul>		</ul>
	===Reserved characters allowed in ~~field~~ names with special syntax===		===Reserved characters allowed in names with special syntax===
	<p>If any of the reserved characters listed in [[#Reserved characters allowed in ~~field~~ names with special syntax\|Reserved characters allowed in ~~field~~ names with special syntax]] is embedded in a ~~field~~ name, the character must be part of a quoted string. When forming ~~field~~ names, avoid the following characters.</p>		<p>If any of the reserved characters listed in [[#Reserved characters allowed in names with special syntax\|Reserved characters allowed in names with special syntax]] is embedded in a name, the character must be part of a quoted string. When forming names, avoid the following characters.</p>
	<table>		<table>
	<caption>Reserved characters allowed with special syntax</caption>		<caption>Reserved characters allowed with special syntax</caption>
Line 37:		Line 39:
	</tr>		</tr>
	</table>		</table>
	===Reserved characters not allowed in ~~field~~ names===		===Reserved characters not allowed in names===
	<p>The special characters listed in [[#Reserved characters not allowed in ~~field~~ names\|Reserved characters not allowed in ~~field~~ names]] cannot be used in ~~field~~ names.</p>		<p>The special characters listed in [[#Reserved characters not allowed in names\|Reserved characters not allowed in names]] cannot be used in names.</p>
	<table>		<table>
	<caption>Reserved characters not allowed in ~~field~~ names</caption>		<caption>Reserved characters not allowed in names</caption>
	<tr>		<tr>
	<td>??</td>		<td>??</td>
Line 59:		Line 61:
	</table>		</table>
	<p>Note</p>		<p>Note</p>
	<p>The delete (@) and flush (#) characters used at an installation are controlled by the ERASE and FLUSH ~~parameters, described in the <var class="product">Model 204</var> Parameter and Command Reference~~. If different symbols are chosen, the restriction on using these characters in field names applies to the new symbols.</p>		<p>The delete (@) and flush (#) characters used at an installation are controlled by the [[ERASE parameter\|ERASE]] and [[FLUSH parameter]]s. If different symbols are chosen, the restriction on using these characters in field names applies to the new symbols.</p>
	<b>Examples</b>		<b>Examples</b>
	<p>Some examples of valid field names are:</p>		<p>Some examples of valid field names are:</p>
Line 75:		Line 77:
	3JULY95		3JULY95
	</p>		</p>
	===Reserved words requiring special attention in ~~field~~ names===		===Reserved words requiring special attention in names===
	<p>The following conditions apply to the reserved words or operators listed in [[#Reserved words requiring special attention in ~~field~~ names\|Reserved words requiring special attention in ~~field~~ names]]: </p>		<p>The following conditions apply to the reserved words or operators listed in [[#Reserved words requiring special attention in names\|Reserved words requiring special attention in names]]: </p>
	<ul>		<ul>
	<li>The word can be part of an unquoted string as long as it is not surrounded by spaces:</li>		<li>The word can be part of an unquoted string as long as it is not surrounded by spaces:</li>
Line 145:		Line 147:
	</tr>		</tr>
	</table>		</table>
	<b>Using reserved words or characters in ~~field~~ names</b>		<b>Using reserved words or characters in names</b>
	<p>If you do use reserved words or characters as part of a field name, you can reference the field names by enclosing the field name with the reserved word or character in single quotation marks. The following example uses a field name called NOR SLS:</p>		<p>If you do use reserved words or characters as part of a field name, you can reference the field names by enclosing the field name with the reserved word or character in single quotation marks. The following example uses a field name called NOR SLS:</p>
	<p class="code">FIND ALL RECORDS WITH 'NOR SLS' = 100000...		<p class="code">FIND ALL RECORDS WITH 'NOR SLS' = 100000...

Rob at 23:30, 17 April 2013

2013-04-17T23:30:46Z

@@ Line 1: / Line 1: @@
 ==Field name rules==
 <p>Every field in a <var class="product">Model&nbsp;204</var> file has a field name by which it is referenced. The following restrictions apply to field names:</p>
@@ Line 171: / Line 153: @@
 </p>
 [[Category:File manager]]

ELowell: /* Designating fields */

2013-03-22T20:14:24Z

Designating fields

← Older revision		Revision as of 20:14, 22 March 2013
Line 11:		Line 11:
	<p>As the file designer, your responsibility is to make informed decisions concerning these issues based on knowledge of the data and required results. In so doing, you can have a dramatic effect on the efficiency with which <var class="product">Model 204</var> runs.</p>		<p>As the file designer, your responsibility is to make informed decisions concerning these issues based on knowledge of the data and required results. In so doing, you can have a dramatic effect on the efficiency with which <var class="product">Model 204</var> runs.</p>
	==Designating fields==		==Designating fields==
	<p>When setting up a <var class="product">Model 204</var> file, you must ~~first~~ decide what fields the records will contain. A record in a personnel file, for instance, might contain a Social Security number field, a last name field, a spouse's name field, and so on. </p>		<p>When setting up a <var class="product">Model 204</var> file, you must decide what fields the records will contain. A record in a personnel file, for instance, might contain a Social Security number field, a last name field, a spouse's name field, and so on. </p>
	===Variable record formats===		===Variable record formats===
	<p>Each record is not required to have a value for every field; record format is variable. If an employee's address is unknown, for example, the address field can be left out of the record altogether and some disk space is saved. However, if preallocated fields are specified for a file, space is reserved in each record for all the preallocated fields. (See "Preallocated fields".) </p>		<p>Each record is not required to have a value for every field; record format is variable. If an employee's address is unknown, for example, the address field can be left out of the record altogether and some disk space is saved. However, if preallocated fields are specified for a file, space is reserved in each record for all the preallocated fields. (See "Preallocated fields".) </p>
	===Multiply occurring fields===		===Multiply occurring fields===
	<p>Most types of fields can be multiply occurring, that is, have more than one value per record. For example, the CHILD field can appear several times in one record. </p>		<p>Most types of fields can be multiply occurring, that is, have more than one value per record. For example, the CHILD field can appear several times in one record. </p>

	==Field name rules==		==Field name rules==
	<p>Every field in a <var class="product">Model 204</var> file has a field name by which it is referenced. The following restrictions apply to field names:</p>		<p>Every field in a <var class="product">Model 204</var> file has a field name by which it is referenced. The following restrictions apply to field names:</p>