Why not just suppress the heading? HDR.SUP David A. Green DAG Consulting
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Bill Haskett Sent: Wednesday, January 18, 2006 5:20 PM To: [email protected] Subject: [U2] [UD] list output when captured I've got a simple scroll routine that parses the output from a LIST or SORT command's "CAPTURING" variable of an EXECUTE statement. The routine tests for the 2nd empty line to determine when the column heading ends and the data begins, as all output with a heading puts a blank line between the column heading and the data. So, typical captured output would look like: SCRATCH(1)=Dictionary of File: PERIPHERALS 16:05:08 Jan 18 2006^Dict Name...... Typ # Col-Heading.... Field-Def... Conversion.. Formt Assoc ...^^@ Phr LPTRNO DEV_N^ . . The total width of the heading is 78 characters, while the TERM width is 79. If I were to change the TERM width to 78 then rerun the above listing the extra line between the column heading and the 1st row of data disappears (the first of two attribute marks changes to a space). SCRATCH(1)=Dictionary of File: PERIPHERALS 16:05:08 Jan 18 2006^Dict Name...... Typ # Col-Heading.... Field-Def... Conversion.. Formt Assoc ... ^@ Phr LPTRNO DEV_N^ . . Is there a reason why this occurs (I've not seen this before) or will I just have to be careful in the future? As always, thanks. Bill Haskett ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list [email protected] To unsubscribe please visit http://listserver.u2ug.org/
