View Single Post
Old 06-26-2016, 07:47 PM   #167
davidfor
Grand Sorcerer
davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.davidfor ought to be getting tired of karma fortunes by now.
 
Posts: 24,905
Karma: 47303824
Join Date: Jul 2011
Location: Sydney, Australia
Device: Kobo:Touch,Glo, AuraH2O, GloHD,AuraONE, ClaraHD, Libra H2O; tolinoepos
From the error, the "date read" column is a custom column that is stored as a date. Something is wrong with the formatting of the date in the record that fails. I assume that is the "260'ish" book. The error suggests that the date parsing routine is getting something that looks like a timestamp, but it has a number greater than 23 in the hour part of the timestamp.

If you cannot find the problem record, post the file and I will have a look. If you can find it, I would still like to see the problem record. From it, I might be able to make the date parsing more robust.
davidfor is offline   Reply With Quote