Section 13: Inquiry Processes
Inquiry Processes
(from SP2 Output Functions invoked as INQUIRY)
Item 13.1
Conversion Bug (fixed in V05): In V04 the first two lines of code in the SP2 Output Start of Function, if any, are lost (overwritten) when an output is converted to an inquiry process in APPX. The conversion writes two sets of identical code in Start of Process with the exception that the first set uses 1/0 for flags while the second set uses Y/N.
Item 13.2
Note: In general, APPX inquiry processes suffer from the same problems that APPX output processes do except that those converted from SP2 are not associated with a query (since SP2 cannot link a sort to an output invoked as an INQUIRY). These problems should be addressed for the inquiry when addressing the output. The V05 conversion log for Inquiry Functions warns whenever SP2 outputs are converted to APPX inquiry processes or to both APPX inquiry/output processes.
Item 13.3
Bug (FYI): APPX technical documentation for inquiries is incomplete.
Item 13.4
Difference (flagged in V05): APPX presents a key entry screen upon entry and exit from an inquiry on a one-record file whereas SP2 does not. If desired, this screen can be suppressed in APPX by defining a logic work field 'WORK DISPLAY' with default "N" and adding the following to Select Image of the Key Entry frame:
IF aaa WORK DISPLAY EQ 0 T SET aaa WORK DISPLAY = 1 T SET --- OPTION = RETURN F SET --- OPTION = END
This approach will remove access to print disposition but SP2 does not offer this either.
Item 13.5
Difference (fixed in V05): Outputs designed for the screen were limited to 79 columns in SP2. Change these to 80 columns in APPX to avoid possible editing errors.
Item 13.6
Bug (fixed in APPX 2.3): APPX 1.8.4 holds the record returned as the next key in an inquiry. (Note: In APPX 2.3 the screen may show CHG Mode but the MODE value is actually INQUIRE so the record is not held.)