Whether QM correctly calculates dates?

Generic selectors
Exact matches only
Search title only
Search in content
Search in all posts
Search in pages
Answers
Questions
0

Hi all.
Excel’s Date(), Eomonth() and Edate() are correctly calculate the beginning and the end dates for the months of 1900 year.
Why QM’s Date(), Eomonth() and Edate() can’t do the same? Or what am I doing wrong?
Thank you in advance for your help.
See the model file:
QM5.3.4 Date Functions wrong calcs. SAU.model

Edited question
0

Dear SAU,

Thanks for your feedback. We will look into this problem with those functions as soon as possible.

Kind regards,
Brian

0

Hi Brian,
Firstly, I thank you for your answer.
Secondly, I want to communicate you the following information:

  1. QM5.3.4’s Date(), Eomonth() & Edate]() INCORRECTLY calculate the start & end dates of months in the range [1900 – 2011] yrs.
  2. QM5.3.4’s Date(), Eomonth() & Edate()       CORRECTLY calculate the start & end dates of months in the range  [2012 – 9999] yrs.
  3. QM4.x’s    Date(), Eomonth() & Edate()       CORRECTLY calculate the start & end dates of months in the range  [1900 – 2011] yrs.

I am convinced it is necessary to release a fix for QM5.3.4 in the date functions calculation part. If this is not done, it is not possible to work with containing historical data models.
I attached the model file:

Edited answer
0

Dear Sau,

The issue is that there is a bug in the Excel date in the year 1900. Excel incorrectly counts 1900 as a leap year. See https://support.microsoft.com/en-us/kb/214326. This can be seen in the model I am attaching, The last day of February is 59 and the first day of march is 61. Quantrix made a conscious decision to not replicate that bug, so dates before March 1, 1900 will not match between Quantrix and Excel.

Thank you for your question.

Brian

Latest Questions