|
Vern, Sorry for the late reply. In QMQRY: Not really, you can indicate BREAKx (where x is 1 to 9, indicating the breaking level) or OMIT. I would try to OVRPRTF the SPLF of QMQRY a liitle smaller than the report length and place the Token field at the end. It may then produce two SPLF's,and the last one can be removed. (Default page width is 80) QMQRY is part of the SQL Development kit. If it is installed it is on his system. We do not have Query/400 on our system, unfortunately. So from memory lane: You can tell the field to be field 0 in the result set and it will not print, but it might be used as a break level field at the same time. It is possible to turn a QRYDFN (Query/400) into a QMQRY object with RTVQMQY QRYDFN(*YES) and CRTQMQRY using a source file. A form can also be created with a source file, but that is very trickyand obscure. Midrange Computing had an article on it, see www.mcpressonline.com. Otherwise, if the field is on the page, let them ignore it. Regards, Carel Teijgeler *********** REPLY SEPARATOR *********** On 20-11-02 at 16:52 Vern Hamberg wrote: >Carel, you beat me to it. But he is using Query/400, not Query Manager. > >Can you suppress the Token column in the form - it'd be nice not to see it. > >At 09:39 PM 11/20/2002 +0100, you wrote: >>Mark, >> >>I think others have suggested it (I threw away the posts, after quickly >>reading them), but I would think in the line of : >> >>SELECT fields, 'A' AS Token >>FROM file >>WHERE SUBSTR(fielda, 1, 1) <> 'X' AND SUBSTR(fielda, 1, 3) <> 'DSL' >>UNION >>SELECT fields, 'B' AS Token >>FROM file >>WHERE SUBSTR(fielda, 1, 3) = 'DSL' >>UNION >>SELECT fields, 'C' AS Token >>FROM file >>WHERE SUBSTR(fielda, 1, 1) = 'X' >>ORDER BY Token, fields >> >>With Query Manager you can create a FORM with Token as the Break Level.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2025 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.