No, that is a compatibility setting for older 4D versions where time values were converted to milliseconds instead of seconds. Hoping some day there will be an option to just use time values instead of numbers. That was done for dates (instead of strings), seems like it should be possible for time. The type conversion rules for objects and collections seem crazy and inconsistent.
John DeSoi, Ph.D. > On Mar 27, 2020, at 1:19 PM, kculotta via 4D_Tech <4d_tech@lists.4d.com> > wrote: > > Would this affect the display? > https://doc.4d.com/4Dv18/4D/18/Database-Parameters.302-4504404.en.html > section "Times inside objects " ********************************************************************** 4D Internet Users Group (4D iNUG) Archive: http://lists.4d.com/archives.html Options: https://lists.4d.com/mailman/options/4d_tech Unsub: mailto:4d_tech-unsubscr...@lists.4d.com **********************************************************************
