Activate: popup page execute after the page activate event eg: enabling a field, hiding a scroll area,hiding

the page note: This event is valid only for pages that are defined as standard or seconda ry. This event is not supported for subpages. FieldChange: eg: recalculate page field values, change the appearance of page controls FieldChange PeopleCode is often paired with RowInit PeopleCode FieldDefault : sets fields by default when new data is being added to the component; ie, in Add mode and when a new row is inserted into a scroll area. note: IsChanged property for the row is set to True Note. An error or warning issued from FieldDefault PeopleCode causes a runtime e rror. FieldEdit: to validate the contents of a field should display a message using the Error statement,displaying an error message a nd turning the field red. note:To permit the field edit but alert the user to a possible problem, use a Warning statement instead of an Error statement. Warning statement displays a warning dialog box with OK and Explain buttons. FieldFormula : FUNCLIB_ (function library) ItemSelected: is initiated whenever a user selects a menu item from a pop-up menu. PostBuild : used to hide or unhide pages. It is also used to set component variables. PreBuild: This event is often used to hide or unhide pages. It is also used to set compone nt variables. PrePopup: is initiated just before the display of a pop-up menu. eg: PrePopup PeopleCode to control the appearance of the pop-up menu. RowDelete: a user attempts to delete a row of data from a page scroll area. Note. RowDelete does not trigger programs on derived/work records. RowInit: initiated the first time that the Component Processor encounters a row of data RowInit PeopleCode is often paired with FieldChange PeopleCode. RowInsert: insertion of new rows. Note :Do not put PeopleCode in RowInsert that already exists in RowInit, because a RowInit event always initiates after the RowInsert event, which will c ause your code to be run twice. RowSelect : RowSelect PeopleCode is used to filter out rows of data as they are being read i nto the component buffer.

note: A DiscardRow function in RowSelect PeopleCode causes the Component Process or to skip the current row of data and continue to process other rows. A StopFetching statement causes the Component Processor to accept the current r ow of data, and then stop reading additional rows. SaveEdit: Whenever a validation involves more than one component field, you should use Sav eEdit PeopleCode. If a validation involves only one page field, use FieldEdit PeopleCode. note :Use the SetCursorPos function to set the cursor position to a specific pag e field following a warning or error in SaveEdit, to show the user the field that is causing the problem SavePostChange: After the Component Processor updates the database, it initiates the SavePostCha nge event. You can use SavePostChange PeopleCode to update tables not in your component us ing the SQLExec built-in function. Note: The system issues a SQL Commit statement after SavePostChange PeopleCode c ompletes successfully. Important: Never issue a SQL Commit or Rollback statement manually from within a SQLExec function. Let the Component Processor issue these SQL commands. SavePreChange: SavePreChange PeopleCode provides one final opportunity to manipulate data befor e the system updates the database. SearchInit : SearchInit triggers associated PeopleCode in the search key fields of the search record. note: SearchInit and SearchSave events will only execute if the Allow Search Eve nts for Prompt Dialogs checkbox was selected for the search key s record field pro perties in Application Designer. By default Allow Search Events for Prompt Dialo gs is off. SearchSave: