|
Good point - QMFORMs are marvelous creatures! STRQM is about the only
way I want to work with them. Just try RTVQMFORM over an existing
*QRYDFN and see the results - source file needs to be 162 long, BTW. The
source for QMFORMs is at least nasty!
There are some really nice capablities 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, it creates multiple sets, so all data
is available - a bit ugly, but there, nonetheless.
On 7/3/2013 6:22 AM, rob@xxxxxxxxx wrote:
I never played around with customizing forms in qmqry (aka Query
Management). Which may be a decision maker in qmqry vs QSH DB2 for
displaying results.
Rob Berendt
-- IBM Certified System Administrator - IBM i 6.1 Group Dekko Dept
1600 Mail to: 2505 Dekko Drive Garrett, IN 46738 Ship to: Dock 108
6928N 400E Kendallville, IN 46755 http://www.dekko.com From: Vernon
Hamberg <vhamberg@xxxxxxxxxxxxxxx> To: Midrange Systems Technical
Discussion <midrange-l@xxxxxxxxxxxx>, Date: 07/03/2013 07:16 AM
Subject: Re: AW: how to use sql distinct in CL? Sent by:
midrange-l-bounces@xxxxxxxxxxxx Yes, as I said in my post, if one
wants a table, use RUNSQL or RUNSQLSTM (before 7.1, if you don't have
RUNSQL). If the goal is to _display_ the results, QMQRY is the easiest
way, or maybe the QShell db2 function. I don't know if the db2
function allows SELECT. Vern
--
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.
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 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.