JAL: add link

2018-03-12T16:16:56Z

add link

← Older revision		Revision as of 16:16, 12 March 2018
Line 1:		Line 1:
	{{Template:M204.1702 skeleton}}		{{Template:M204.1702 skeleton}}
	<P>		<P>
	The request has attempted to add an occurrence of a fieldname=value pair for a unique field (via ~~ADD~~, ~~INSERT~~, ~~CHANGE~~ or ~~STORE RECORD~~) and that fieldname=value pair already exits in another record in the file. The requested update will not be performed. </p>		The request has attempted to add an occurrence of a fieldname=value pair for a unique field (via <var>Add</var>, <var>Insert</var>, <var>Change</var>, or <var>Store Record</var>) and that fieldname=value pair already exits in another record in the file. The requested update will not be performed. </p>
	<p>		<p>
	This message is issued only when no ~~ON FIELD CONSTRAINT CONFLICT~~ unit exists for the request. The request will be canceled and its active transaction (if any) will be backed out. </P>		This message is issued only when no <var>[[On units\|On Field Constraint Conflict unit]]</var> exists for the request. The request will be canceled and its active transaction (if any) will be backed out. </P>
	<p>		<p>
	<b>Response:</b> Procedures that update unique fields should always contain ~~ON FCC~~ units to handle uniqueness conflicts when they occur. Decisions about how to handle uniqueness conflicts should be made on an application by application		<b>Response:</b> Procedures that update unique fields should always contain <var>On Fcc</var> units to handle uniqueness conflicts when they occur. Decisions about how to handle uniqueness conflicts should be made on an application by application basis.
	basis. </p>		</p>
	{{Template:M204.1702 footer}}		{{Template:M204.1702 footer}}
	<!-- skeleton as it was in pdf/UNIQUENESS VIOLATION DETECTED FOR fieldname = value IN FILE filename /-->		<!-- skeleton as it was in pdf/UNIQUENESS VIOLATION DETECTED FOR fieldname = value IN FILE filename /-->

DmeWiccan: Automatically generated page update

2018-03-07T15:56:50Z

Automatically generated page update

New page

{{Template:M204.1702 skeleton}}

The request has attempted to add an occurrence of a fieldname=value pair for a unique field (via ADD, INSERT, CHANGE or STORE RECORD) and that fieldname=value pair already exits in another record in the file. The requested update will not be performed. 

This message is issued only when no ON FIELD CONSTRAINT CONFLICT unit exists for the request. The request will be canceled and its active transaction (if any) will be backed out. 

Response: Procedures that update unique fields should always contain ON FCC units to handle uniqueness conflicts when they occur. Decisions about how to handle uniqueness conflicts should be made on an application by application
basis. 
{{Template:M204.1702 footer}}

M204.1702 - Revision history

JAL: add link

DmeWiccan: Automatically generated page update