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



Attempting to learn SQL by RTVQMQRY is a very bad idea.
For one thing, Query/400 will not show you any decent joins. What little
joins they show you are done via where clauses. On exception joins and
what not the RTVQMQRY just fails outright.
For another thing, getting the subtotals as shown by Query/400 is not
possible with the logic shown by RTVQMQRY. As Chuck said, you will have
to make a decision as to whether or not you want the subtotals right there
in your view by using grouping sets, ROLL UP, CUBE, and whatever that
genre is called. Or, if you want your view to get the details and your
Query can then do the subtotals off of that view.

But I do agree that view will make much more sense to many of your users
than having to figure out all the joins themselves,
calculating many derived columns (like onHand is equal to opening balance
+ receipts - issues + adjustments),
and converting many confusing 6 character column names to more meaningful
column names. MYFILA, MYFILB, MYFILC, MYFILD becomes ItemNbr, ItemDesc,
OnHand, AllocQty


Rob Berendt

As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.