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



Is Excel treating 2000 as a leap year? It wasn't. I know there were
problems where Excel didn't properly handle leap years in the past, but I
thought this was fixed in more recent versions.

"RPG400-L" <rpg400-l-bounces@xxxxxxxxxxxx> wrote on 09/17/2015 01:00:02
PM:
----- Message from "Englander, Douglas"
<Douglas_Englander@xxxxxxxxxxxxx> on Thu, 17 Sep 2015 11:56:52 -0500
-----

To:

"rpg400-l@xxxxxxxxxxxx" <rpg400-l@xxxxxxxxxxxx>

Subject:

RPG date functions vs. Excel date functions


I am reading an excel spreadsheet via RPG (using Scott Klements
routines). There is one cell containing the number 40999, which
excel interprets as March 31, 2012. The 40999 representing the
number of days from January 1, 1900 (January 1, 1900 would be
represented as 1).

If I initialize a base date in RPG (a *ISO date field) to December
31, 1899, and add the excel number to it (converted to days), I am
expecting to get the date that excel is converting 40999 to (i.e. I
would expect RPG to calculate December 31, 1899 + %days(40999) to be
March 31, 2012 also). However, no matter how I do it, RPG calculates
December 31, 1899 + %days(40999) to be April 1, 2012.

Does anyone have any idea as to why the calculations differ by one
day? I trust IBM over Microsoft, and would take the April 1, 2012
date, but I would like to know why the two dates are calculated
differently.

Thank you,

Doug


As an Amazon Associate we earn from qualifying purchases.

This thread ...

Follow-Ups:

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.