Page 1 of 1

datenext bug

Posted: Tue Mar 20, 2018 7:27 am
by radmirer
Hi,

I found that datenext is not working properly using monthly data. For example, while the first command below gives the correct result on my comupter, the command below does not. I was able to reproduce this on other computers as well:

show @datenext(@dateval("1995M01"), "mm")
show @datenext(@dateval("2000M03"), "MM")

Regards

Re: datenext bug

Posted: Tue Mar 20, 2018 7:31 am
by EViews Gareth
What result did it give you that was incorrect?

I just ran it on my PC and it gave the correct date (2000/04/01)

Re: datenext bug

Posted: Tue Mar 20, 2018 9:56 am
by smr01
It seems to only be an issue with M3, M6, M9 and M12

M3 gives me 2000Q2, M6 200S2 M9 2000Q4 and M12 2001

Re: datenext bug

Posted: Tue Mar 20, 2018 10:00 am
by smr01
Oops using EViews 10 Enterprise March 15 2018 build

Re: datenext bug

Posted: Tue Mar 20, 2018 10:12 am
by EViews Gareth
Note that the function will return a date. As in a single day.

2000Q2 is the same thing as 2000M6, which is the same thing as 2000/06/01.

If you would like the result shown in a different date format, change the display format in which you are displaying the date.