×
The internal search function is temporarily non-functional. The current search engine is no longer viable and we are researching alternatives.
As a stop gap measure, we are using Google's custom search engine service.
If you know of an easy to use, open source, search engine ... please contact support@midrange.com.
Yes, one could say that QM neither wraps nor truncates - wrapping a long line just looks messy to me - very hard to read by this human!
So I do like the behavior of QM, where it creates sets of spooled files - if the PRTF is 80 wide, say, and the report is 198, there will be 3 sets of reports - each will try to include full columns up to the width of the PRTF. Also not the easiest as to putting it all together, but at least everything IS there with wrapping.
I'm interested in a comparison of column formatting between the 2 products, by the way - could be useful for the archives.
Vern
----- Original Message -----
On 03 Jul 2013 06:34, Vernon Hamberg wrote:
<SNIP>> There are some really nice capabilities with QMFORMs - some
formatting options (word wrap in a column, e.g.), more flexibility
than Query/400 queries. And if the report is wider than your printer
file, it doesn't just truncate, as Query/400 does <<SNIP>>
Query/400 offers some column formatting features that QM does not,
but indeed has no column wrapping. Contrary to the apparent implication
above, the Query/400 is not limited to its default behavior of
truncating data exceeding line\printer-file width. The Query/400 report
writer feature includes a capability of line wrapping, which AFaIK, is
not available with a QM Form.
midrange.com
