Note: variable names are not supported to start with a number ($4dDate)
the line
OB SET($obj;"apiDate";"2019-02-24")
does not set a date value.
it sets a string that looks like a date to some people.
try something like
$obj:=New object
OB SET($obj;"d1";Current date)
OB SET($obj;"d2";"2019-02-
Thanks Jeremy,
I turned on the compatibility setting for "Use date type instead of ISO date
format in objects" and restarted 4D, but still get the same results from the
code below. Even if the setting did result in the correct answer, I think that
4D made a bad decision to make the default beh
Hi Bart,
If you store a date in an Object as a string, 4D interprets that date as a UTF
date.
So “2019-02-24” (giving only the date but not time) is interpreted as midnight
on the 24th. That is at the stroke of midnight when the 24th day **starts**.
When you retrieve the value around 6:30 PST
I just discovered what I think is a serious bug with 4D reading dates from an
object.
If you store a 4D date value in an object and retrieve it the value is correct.
However, if you retrieve a date that is stored in the format -MM-DD, the
date returned is one day less that the date store
4 matches
Mail list logo
