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

Even though I'm a complete novice with Query/400, I decided to try modeling the customer's situation.

I found that if the date format for the file field is *ISO, there's no problem. But if it's *MDY, it creates the same unreadable "grand total" record the customer was getting.

Just trying things out of the manual, I found that if you define a "result field" thusly:
                             Define Result Fields
Type definitions using field names or constants and operators, press Enter.
  Operators:  +, -, *, /, SUBSTR, ||, DATE...

Field Expression Column Heading DATECHAR CHAR(DATEFLD) DATE

and use DATECHAR in place of DATEFLD in the rest of the query, you avoid the unreadable record, since everything goes into the query summary as a character field. You can also specify how you want the date formatted.

So I guess I've answered my own parting question on this puzzle.

Thanks for all your help.


As an Amazon Associate we earn from qualifying purchases.

This thread ...


Follow On AppleNews
Return to Archive home page | Return to MIDRANGE.COM home page

This mailing list archive is Copyright 1997-2023 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.