|
I have to validate the XQ03 (date) and figure out if it's in the 'correct week' with each record. Depending on the day there could be thousands of header records. I think I can change the way I validate this date, whether it's with TEST or MONITOR. -----Original Message----- From: Booth Martin [mailto:Booth@xxxxxxxxxxxx] Sent: Thursday, May 15, 2003 10:24 AM To: rpg400-l@xxxxxxxxxxxx Subject: RE: Date arithmetic - performance dog? In this instance I might do the (test D E ) followed by getting last week's ending date. If the job date is greater than the last week's date I'd just add 7 days to the answer already gotten. But beyond that.. why do you do it over and over? Once at the beginning of the program would seem plenty. Get the two ending dates and save them as test fields. If job date > last weeks date use this week's date, else use last weeks date. That'd seem to be your biggest saver of time.
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.