problem with eom()

[Richard Kreiss]

> -----Original Message-----
> From: Filepro-list [mailto:filepro-list-
> bounces+rkreiss=verizon.net at lists.celestial.com] On Behalf Of Kenneth
> Brody
> Sent: Tuesday, October 28, 2014 10:39 AM
> To: Richard Kreiss
> Cc: filepro-list at lists.celestial.com
> Subject: Re: problem with eom()
> 
> On 10/28/2014 12:56 AM, Richard Kreiss wrote:
> [...]
> >>> ExpDate=foobar(12){"/01/"{foobar(13)
> >>>
> >>> Expect ExpDate = "10/31/2013"
> >>
> >> I would expect "10/01/2013".
> >>
> >>> In my processing coming up as "10/31/2014"
> >>
> >> Show the actual processing.
> >>
> >>> Has anyone else seen this problem.  This occurs with EOM();  When I
> >>> put this into a msgbox without eom the date displays correctly.  Use
> >>> EOM and it adds a year to that number.
> >>
> >> I see no "EOM" in the above code.
> >>
> >> Ok, Ken, I left out
> > Eom(foobar(12){"/01/"{foobar(13))
> >
> > The result should be in year 2013. It comes 2014.
> >
> > I just wanted to know if anyone else experienced this problem.
> 
> The problem is that you are not passing a date to EOM().  Rather, you are
> simply passing it a string that "looks" like a date -- "10/01/2013".  And, even
> then, is it "October 1" or "January 10"?  Because you are not passing it a date,
> you get the EOM of the current date, which coincidentally is also October.


> ExpDate = foobar(12){"/01/"{foobar(13)
> ExpDate = EOM(ExpDate)

Here is an interesting twist to what you are indicating, when I run the same programming in 5.7.4.06, the programming works properly.

Richard