Why does 4GL generate invalid dates when it performs arithmetic with months?
When 4GL adds months to a date, it sometimes ends up with a invalid date: January 31st + 1 UNITS MONTH = February 31st Doh! There is no February 31st! There are those who argue that 4GL should evaluate the above to February 28th (or 29th if it’s a leap year), and others who feel it should return a date sometime in early March. The fact is that it doesn’t make either of these decisions for you, and it never will. Write your own routine instead, and make it do whatever your business considers most appropriate. jparker@boi.hp.com (Jack Parker) wrote: Some of you will run into this today…..
Related Questions
- When I am on certain dates in the calendar on the Availability screen I get a message that says "Invalid Property Array Index set spread colors"?"
- Where can I check the historical currency exchange rates, from dates older than two months?
- Why does 4GL generate invalid dates when it performs arithmetic with months?
