JDE Form开发.ppt

12_ERFlow * Processing pauses so that the developer can add logic if he/she wishes. At this point, FC is blank. After the verify has occurred but before the record is truly deleted, you can still attach logic. 12_ERFlow * Processing pauses so that the developer can add logic if he/she wishes. At this point, FC is blank. You can add logic just before the record is deleted 12_ERFlow * Processing pauses so that the developer can add logic if he/she wishes. At this point, FC is blank. The SQL DELETE happens at this point. 12_ERFlow * Processing pauses so that the developer can add logic if he/she wishes. At this point, FC is blank. You can also add logic after the record is physically deleted from the database. 12_ERFlow * Processing pauses so that the developer can add logic if he/she wishes. At this point, FC is blank. If multiple lines are being deleted, you can attach logic at this point. 12_ERFlow * This is a graphical representation of what’s in the runtime structures just BEFORE “write grid line after” is run. 12_ERFlow * For a Find/Browse form, these are possible reasons you might use this event point. 12_ERFlow * It’s important to emphasize that records are read in from the database one at a time. Each record passes through the same processing steps. 12_ERFlow * This slide is a graphical representation of the while loop process. Note that it’s now record 47 being read in. 12_ERFlow * This slide is a graphical representation of the while loop process. Note that it’s now record 47 being read in. 12_ERFlow * This slide is a graphical representation of the while loop process. Note that it’s now record 47 being read in. 12_ERFlow * This slide is a graphical representation of the while loop process. Note that it’s now record 47 being read in. 12_ERFlow * This slide is a graphical representation of the while loop process. Note that it’s now record 47 being read in. 12_ERFlow * This slide is a graphical representation of the while loop proce