In Use the Section Editor, you saw some of the procedural code that gets the window up and running, such as the enable_UI procedure, but not the code that defines all the objects in the window. Take a look at that now. As before, since the AppBuilder generates and maintains that code for you based on how you lay out objects in the design window, it does not show the code to you in the Section Editor.

To view the entire procedure, you can select either Compile > Code Preview again or File > Print from the AppBuilder’s main menu to print a hard copy of the entire procedure.

Now look through the entire procedure to see some of the syntax that defines the window and its contents. If you look at a printed listing of the procedure file (or open the file outside of the AppBuilder), you notice numerous ANALYZE-SUSPEND and ANALYZE-RESUME preprocessors mixed in with the code. The AppBuilder uses these to separate out code it has generated and maintains for you from code you can add to the procedure yourself. These are stripped out of the Code Preview listing for you, making it a little easier to read. Just try to look beyond these things for the time being to learn what the statements are that really define the window.