Page History
[ 
|../../index.htm#lansa/frmeng01_0220.htm]
You are here:
...
Important Observations
- GROUP_BY commands help you simplify your code.
- You should always check the I/O status after performing database operations. The IF_STATUS command supports *OKAY, *ERROR, *VALERROR, *NORECORD, *ENDFILE, *BEGINFILE, *EQUALKEY, *NOTEQUALKEY.
- Program level validation rules can be added using a BEGINCHECK / ENDCHECK and related validation commands CALLCHECK, CONDCHECK, DATECHECK, FILECHECK, RANGECHECK, VALUECHECK, IF_ERROR, SET_ERROR.
- A record should be fetched from the database prior to updating or deleting it, if you are not using a key to identify the record. For more details about cross-update and delete, please refer to DELETE Comments / Warnings and Understand the UPDATE Command in UPDATE Comments / Warnings in the Technical Reference Guide.
- LANSA provides many Built-In Functions that can be used to perform specialized tasks in LANSA. Intrinsic field methods are now used in place of many of these Built in Functions.
- The SUBROUTINE / ENDROUTINE defines a routine that you can EXECUTE from any other routine in your form. Subroutines cannot be defined within an event, method or property routine.
...
- How to use the FETCH, INSERT, UPDATE and DELETE database commands.
- How to handle errors using the IF_STATUS command when performing table operations.
- How to code program level validations using BEGINCHECK / ENDCHECK, CONDCHECK, FILECHECK, RANGECHECK, VALUECHECK, IF_ERROR, and SET_ERROR.
- How program validations relate to the repository validation performed by the Object Access Modules (OAM).
- How to use a Built-In Function to display a message box with user confirmation.
...
- .
...