Laura: /* Error Traps: */

2013-01-24T18:03:17Z

Error Traps:

← Older revision		Revision as of 18:03, 24 January 2013
Line 3:		Line 3:
	===Error Traps:===		===Error Traps:===
	LOCKED traps two types of errors:		LOCKED traps two types of errors:
	1.) the record is locked at another workstation (error code [[0061]])		:1.) the record is locked at another workstation (error code [[0061]])
	2.) file- sharing rules are violated (error code [[4148]])		:2.) file- sharing rules are violated (error code [[4148]])
	LOCKED should be listed before the IOERR or ERROR error conditions when it appears in a list of error conditions, as IOERR and ERROR will trap all the errors that LOCKED traps plus many more. When error processing is handled at the ON error statement level, however, Business Rules automatically invokes the error action which is most specific to the error which has occurred.		LOCKED should be listed before the IOERR or ERROR error conditions when it appears in a list of error conditions, as IOERR and ERROR will trap all the errors that LOCKED traps plus many more. When error processing is handled at the ON error statement level, however, Business Rules automatically invokes the error action which is most specific to the error which has occurred.

Laura: Created page with "The LOCKED error condition can be used at the end of a program statement, in the Exit statement, and in the ON error statement. ===Error Traps:=== LOCKED traps two types of e..."

2013-01-24T17:46:17Z

Created page with "The LOCKED error condition can be used at the end of a program statement, in the Exit statement, and in the ON error statement. ===Error Traps:=== LOCKED traps two types of e..."

New page

The LOCKED error condition can be used at the end of a program statement, in the Exit statement, and in the ON error statement.

===Error Traps:===
LOCKED traps two types of errors:
1.) the record is locked at another workstation (error code [[0061]])
2.) file- sharing rules are violated (error code [[4148]])
LOCKED should be listed before the IOERR or ERROR error conditions when it appears in a list of error conditions, as IOERR and ERROR will trap all the errors that LOCKED traps plus many more. When error processing is handled at the ON error statement level, however, Business Rules automatically invokes the error action which is most specific to the error which has occurred.

<noinclude>
[[Category:Error Conditions]]
</noinclude>

Locked Error Cond - Revision history

Laura: /* Error Traps: */

Laura: Created page with "The LOCKED error condition can be used at the end of a program statement, in the Exit statement, and in the ON error statement. ===Error Traps:=== LOCKED traps two types of e..."