View Single Post
Old 09-11-2013, 12:03 PM   #8
SampleAndy
Addict
SampleAndy ought to be getting tired of karma fortunes by now.SampleAndy ought to be getting tired of karma fortunes by now.SampleAndy ought to be getting tired of karma fortunes by now.SampleAndy ought to be getting tired of karma fortunes by now.SampleAndy ought to be getting tired of karma fortunes by now.SampleAndy ought to be getting tired of karma fortunes by now.SampleAndy ought to be getting tired of karma fortunes by now.SampleAndy ought to be getting tired of karma fortunes by now.SampleAndy ought to be getting tired of karma fortunes by now.SampleAndy ought to be getting tired of karma fortunes by now.SampleAndy ought to be getting tired of karma fortunes by now.
 
SampleAndy's Avatar
 
Posts: 271
Karma: 644344
Join Date: Oct 2012
Location: Pittsburgh, PA, USA
Device: KPW, KFire HD, KFire, KTD 3g, KT, K4B, K4S, K3g, K3g SO, K2, K1
Quote:
Originally Posted by ixtab View Post
...

Your best bet to (hopefully) fix this is to export the collections to calibre via CM, then manually delete the /var/local/cc.db, restart the device, import from calibre via CM. And in the future, to prevent this from happening again: make any needed adjustments to files before you start filing them into collections.
I'd been having some weird problems all along. At one point not too long ago, I gave up and used the feature in CM to [Delete all collections]. I then used [Create collections from directories] and started from there.

If I understand correctly, (meaning guess) these processes just delete all the records from the database and create new ones, but if the database is corrupted, it would still BE corrupted. The only real solution would be to actually delete the database and start from scratch. If I delete the database, will the Kindle automatically create an empty one or do I need to do something else?

Thanks for your help, as always,
Andy
SampleAndy is offline   Reply With Quote