NO-ERROR has no effect when a STOP or QUIT condition occurs.
If an error object is thrown to a statement that includes the NO-ERROR option, the information and messages in the error object are used to set the ERROR-STATUS system handle.
For more information on using NO-ERROR and error handling in general, see OpenEdge Development: ABL Error Handling.
Assignment (=) statement, ASSIGN statement, BUFFER-COMPARE statement, BUFFER-COPY statement, Class-based method call, COMPILE statement, CONNECT statement, COPY-LOB statement, CREATE automation object statement, CREATE CALL statement, CREATE DATABASE statement, CREATE SAX-ATTRIBUTES statement, CREATE SAX-READER statement, CREATE SAX-WRITER statement, CREATE SERVER-SOCKET statement, CREATE SOCKET statement, CREATE statement, CREATE WIDGET-POOL statement, DDE ADVISE statement, DDE EXECUTE statement, DDE GET statement, DDE INITIATE statement, DDE REQUEST statement, DDE SEND statement, DDE TERMINATE statement, DELETE OBJECT statement, DELETE PROCEDURE statement, DELETE statement, DELETE WIDGET-POOL statement, DISCONNECT statement, DISPLAY statement, DYNAMIC-NEW statement, EXTENT statement, FIND statement, IMPORT statement, EMPTY TEMP-TABLE statement, INSERT statement, LOAD statement, NEW statement, Publish( ) event method, PUT-KEY-VALUE statement, RAW-TRANSFER statement, RELEASE OBJECT statement, RELEASE statement, REPOSITION statement, RUN STORED-PROCEDURE statement, RUN SUPER statement, SAVE CACHE statement, SET statement, SUBSCRIBE statement, Subscribe( ) event method, SUPER system reference, UNLOAD statement, Unsubscribe( ) event method, UPDATE statement, USE statement, VALIDATE statement