× 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.


  1.  Home
  2. MIDRANGE-L
  3. June 2003

Re: edit a *QRYDFN query outside of WRKQRY interface?

Dan

In addition to RTVQMQRY there is RTVQMFORM, which gives you something very close to the QRYDFN output. QRYDFNs can be seen as the combination of the data extraction and the presentation, whereas QMQRY is only extraction and QMFORM is presentation. Results are usually pretty good.

One nice thing, IMO, about QMQRY output is that it creates multiple sets of spooled files when the report width is greater than the PRTF width.

For maintenance, users can use STRQM. There is a part of it (opt 10?) that lets you configure what users can do - whether they can only run in batch, for example, which many have asked about in Query/400, is doable in STRQM. Also, where their queries go. And whether they can change things.

And the interface can be very much like Query/400 - they just need to use F13 to toggle between queries and forms. Or SQL for the queries.

Vern

At 08:20 AM 6/27/2003 -0700, you wrote:
-snip-
Also, some of the queries I support eventually get maintained by endusers, so that precludes QM
queries right there. Besides, if I *really* had my druthers (and had to choose between qmqry and
sql), I'd just convert the *qrydfn's to SQL. Our shop is on a path to learning SQL beyond simple
selects, as I hear the next Lawson version is heavy on SQL.

Bill, you are so right on with the ugly qmqry output. In the past, I have had to change a working
*qrydfn to a qmqry, and the users hated it so much it ended up getting trashed for an RPG program!

Thanks for the suggestions!

- Dan



As an Amazon Associate we earn from qualifying purchases.

This thread ...
Replies:
Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

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.