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



Charles Wilt wrote:
Interesting that Query/38 had this yet Query/400 doesn't.

However if it were me, rather than move backward, I'd move
forward <<SNIP>>

On Tue, Sep 22, 2009 at 1:14 AM, Evan Harris wrote:
I remember doing this in Query on the system/38; I recall
that the trick was to created a calculated field with a
formula of +1.

Query/38 also did tables and there were many occasions I
cursed WRKQRY on the 400 for not having this feature.


The Query/400 carried forward the query & data text merge capabilities & usability of the Sys/36 [a bit too specifically], including support for the IDDU. The three features were required for the S36EE support anyhow. Rather than "enhancing" the S/38 features [which came forward more like a re-compile than the rewrite required for the S/36 code base] to support the deprecated program described files, the ported but re-written S/36 utilities were chosen for usability & compatibility aspects, to support both IDDU for S/36E and DDS for /native/ externally described files. Merging features from the S/38 Query utility into the AS/400 Query utility was not strategic, even if often talked of. Further resources went to any SQL [e.g. QM Query] features, at least until the potential for the concept of client\server [e.g. database access via ODBC by a client giving WYSIWYG instead of green screen] seemed to eclipse most server-based utility enhancements.

Regards, Chuck

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.