B
Bill Wood
Guest
The best section in the documentation to describe this is the section on Data Handling Statements (in the ABL reference). This is online at: documentation.progress.com/.../ This section has a nice chart that shows the relegation between the different data handling statements and how they move data to and from: - the user - the Screen Buffer - the Record Buffer - the database PROMPT-FOR, SET, and UPDATE all ask the user for input but: - PROMPT-FOR just asks the user for input and store the sesult in the Screen Buffer - SET does this as well but also assigns the vale to the record buffer itself - UPDATE does the same as SET but first populates the screen buffer with the current value of the record buffer I would say that 9 times out of 10, in traditional Character or GUI programs where you are collectinginout one FRAME at a time, you are going to use UPDATE instead of SET or PROMPT-FOR. (Note that in Event Driven programming it is actually more common to use DISPLAY, ENABLE and ASSIGN as "single-step" primitive actions because in this model the user has access to many FRAMES and ABL WINDOWS simultaneously and the programmer Iogen wants more fine grained control on when each primative is called. Good luck. BTW there are some good courses on the basics of ABL available (see www.progress.com/.../education)
Continue reading...
Continue reading...