Date errors when assigning date.day > 28 in debug mode and Mac compiled apps

[José_María_Terry_Jiménez]

Hello

I’ve found today that if assigni .day .month and .year to a Date instance returns a wrong day if date.day > 28 (Web App. compiled for Linux Works fine).

If i do (This is on 2013r4.1 on a Mac Running 10.9.1)

Dim TheDate as new Date

TheDate.Day=31
TheDate.Month=1
TheDate.Year=2014

TheDate.SQLDate returns “2014-01-03”

If you do the same with TheDate.Day=30, then TheDate.SQLDate returns “2014-01-02”
For TheDate.Day=29, then TheDate.SQLDate returns “2014-01-01”

And finally for TheDate.Day<=28, then TheDate.SQLDate returns the correct date.

As i told i detected this debugging a Web App on Mac, the compiled version for Linux works fine.

Tried the same with a desktop app and the same happens. The compiled desktop (Mac) app ALSO FAILS!.

Is this some known? I’ve been unable to find something about this in feedback.

Best.

[Wayne_Golding]

It’s one of those peculiarities with Dates. TheDate starts as today 03/02/2014. Setting the day to 31 makes this 3/3/2014, setting the month makes this 3/1/2014. Just always set the Year then Month then Day & you’ll be fine.

[Christian_Schmitz]

Just another topic which shows up every year in February

[Tim_Hare]

This is one of those glitches that seems to come and go. The Date is supposed to be like Schroedinger’s Cat, where it doesn’t resolve until you look at it. In other words, the order you set the values isn’t supposed to matter. But it does. Sometimes.

But why not code it

dim TheDate as new Date(2014, 1, 31)

[José_María_Terry_Jiménez]

@62907:@Wayne Golding

It’s one of those peculiarities with Dates. TheDate starts as today 03/02/2014. Setting the day to 31 makes this 3/3/2014, setting the month makes this 3/1/2014. Just always set the Year then Month then Day & you’ll be fine.

Thank you, that worked. But i don’t understand why it worked right in the Linux compiled app and failed in the MacOSX one.

[Tim_Hare]

I just checked, and it works correctly on Windows, too, so it sounds like a Mac bug.

[Eli_Ott]

The docs state that with an empty constructor you’ll get back today’s date:

When you create and instantiate a Date object, it is initialized to the current date and time. Therefore the order of assignment is important: when dealing with a day that exists in one month when the current system date is in another (such as December 31 when you’re in November), setting the Day before the month can result in an unexpected (here 12/01/2011) or even invalid date. Not setting the year before entering Feb 29 will cause oddities if the current year is not a leap year.

A quick test on Mac OS X, Windows, and Web (on Mac OS X and Windows) gives back the identical date January 3, 2014. Can’t test Linux though.

[Tim_Hare]

Windows 7, Xojo 2013r4.1, I consistently get the correct date, January 31, 2014, with this code:

  dim d as date
  d = new date
  d.day = 31
  d.month = 1
  d.year = 2014
  msgbox d.LongDate

[Christian_Schmitz]

why not use the constructor for passing date valueS?

dim d as new date(2014, 1, 31)