Re: 57nnQU1

I have not looked at this for some time, but believe it is still relevant.
WRKQRY will let you easily format a report wider than 80 columns. STRQM
splits a report wider than 80 columns to 2 different spool files unless you
override the correct printer file.

That is not as easy for an end user to do unless tools are provided.

Jim Essinger
Western Power Sports
Boise ID


On Thu, Sep 25, 2014 at 6:43 AM, Vernon Hamberg <vhamberg@xxxxxxxxxxxxxxx>
wrote:

Rob

I'm curious about something in this post - column formatting - I actually
like what I can do (like wrapping within the column) in STRQM for this -
can you say a little more to compare and contrast the 2 products as to
column formatting? As you undoubtedly know, F13 toggles between the query
and the form, the latter being where the formatting goes.

Thanks
Vern

On 9/25/2014 6:45 AM, rob@xxxxxxxxx wrote:

Are the users using STRSQL?
Do they prefer the selection and prompting of WRKQRY?
Have they tried STRQM as an alternative? (If you have STRSQL you have
STRQM.)
Have they tried STRQM but miss the ease of column formatting with WRKQRY?
Do you have RUNQRY buried into any of your code? Do your vendors require
QU1 be installed because they may have that imbedded?
:-) Are you still running V4 or earlier and have QU1 doing document merge
with OV/400?
Is it worth the savings of dropping QU1 and missing all of this?

I liked the column formatting of QU1 over STRQM. However I forced myself
to stick with STRSQL. The benefit of that was that if I ran into
something that was outside the realm of QU1's 'result fields' I didn't
avoid using that function because it wasn't worth the pain of converting.
And, yes, I know the commands to convert a QU1 query into SQL. I've
written an article on this.

Rob Berendt

--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) mailing list
To post a message email: MIDRANGE-L@xxxxxxxxxxxx
To subscribe, unsubscribe, or change list options,
visit: http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx
Before posting, please take a moment to review the archives
at http://archive.midrange.com/midrange-l.