> > First, get all the other databases done, so you're worried only about the one > which doesn't work. > > Then do the .dump part for that database, putting the output into a file on > disk, which should leave you with a huge file of SQL commands which should > rebuild it. > > It's likely that the .dump stage will fail because your original database is > corrupt. That's your problem. > > If it doesn't fail, split it up into parts, and rebuild your database using > '.read' by reading the parts in one at a time. One of those parts should > cause an error message or a crash. That's your problem. > > Either way, you should be able to narrow down the possible scope for the > crash.
Thank you simon i try this, I read in some forums that .dumb is the best way to repair "malformed" DBs. Do you have an other way?
_______________________________________________ sqlite-users mailing list sqlite-users@sqlite.org http://sqlite.org:8080/cgi-bin/mailman/listinfo/sqlite-users
