That's what I suspected. So to build a slightly better trap, I am doing this:
if tDate is a date and length(tDate) > 5 and tDate contains "/" then put "true" else put "false" end if I am sure there is probably a standard way to catch all possible date formats (excluding "the seconds"), but this works for most. ~Roger On Sat, Oct 14, 2017 at 12:44 PM, Klaus major-k via use-livecode < use-livecode@lists.runrev.com> wrote: > Hi Roger, > > > Am 14.10.2017 um 18:30 schrieb Roger Eller via use-livecode < > use-livecode@lists.runrev.com>: > > > > put "11/20/2017" is a date > > returns true > > ---- > > put "10" is a date > > returns true > > ---- > > put "raccoon" is a date > > returns false > > ---- > > > > WHY is "10" seen as a date? > > looks like the engine is seeing seconds also as a possible valid date. > > convert 0 to long date and long time;put it -> Thursday, January 1, 1970 > 1:00:00 AM > 1:00:00 = DST here in germany! > > convert 10 to long date and long time;put it -> Thursday, January 1, 1970 > 1:00:10 AM > etc... > > And of course: > put (the seconds) is a date -> TRUE > > > ~Roger > > Best > > Klaus > > -- > Klaus Major > http://www.major-k.de > kl...@major-k.de > > > _______________________________________________ > use-livecode mailing list > use-livecode@lists.runrev.com > Please visit this url to subscribe, unsubscribe and manage your > subscription preferences: > http://lists.runrev.com/mailman/listinfo/use-livecode > _______________________________________________ use-livecode mailing list use-livecode@lists.runrev.com Please visit this url to subscribe, unsubscribe and manage your subscription preferences: http://lists.runrev.com/mailman/listinfo/use-livecode
