|
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:
midrange.com
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. -- JHHL
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.
