Try this page as well: http://www.sqlite.org/lang_datefunc.html
Time Strings A time string can be in any of the following formats: 1. *YYYY-MM-DD* 2. *YYYY-MM-DD HH:MM* 3. *YYYY-MM-DD HH:MM:SS* 4. *YYYY-MM-DD HH:MM:SS.SSS* 5. *YYYY-MM-DD**T**HH:MM* 6. *YYYY-MM-DD**T**HH:MM:SS* 7. *YYYY-MM-DD**T**HH:MM:SS.SSS* 8. *HH:MM* 9. *HH:MM:SS* 10. *HH:MM:SS.SSS* 11. *now* 12. *DDDDDDDDDD* On Thu, Apr 27, 2017 at 1:04 PM, Ted Roche <tedro...@gmail.com> wrote: > On Thu, Apr 27, 2017 at 12:17 PM, José Olavo Cerávolo > <jocerav...@yahoo.com> wrote: > > Hi Ted, > > The dates on the existing table are not .NULL..When I get the date using > what you suggested, datetime(yourfield,'unixepoch','localtime'), I get > this date on an MEMO field 1984-10-05 23:00:00. This date is not the actual > date on the other application. The date should be in 2017.The actual value > stored on the actual SQLite table is 459316800. > > Well, that's weird. THE SQLite function datetime() is expecting a > number of 10 digits, so that's not the encoding scheme. Can you use a > tool like SQLite3 to look at the actual data in the SQLite table and > confirm this isn't a problem with ODBC or Fox's intepretation of the > data? > [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://mail.leafe.com/mailman/listinfo/profox OT-free version of this list: http://mail.leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/CAJidMYLCMF8cnUsoXAAGAuaDkrEuTNS-vXwdLGJQ9efy=cw...@mail.gmail.com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
