Each post is given a "record number" when submitted. While the database was down, the system had no way of knowing what record numbers were already used. In at least one case of a thread started during the db downtime, the older thread that already "owned" the record number is the one that came up when I "went to" the new one.

In any case where a db gets "corrupted" the list of which records (posts) belong in which "thread" has to come from data in the database, so it's not too surprising if there are some confused linkups - especially where new data may have been assigned the same recordno as an existing post.(?)

I'm guessing a bit, but each "post" should have a separate number, and there may be some that remain in the database that have lost their links to which "thread" they should be listed with - or in what order. In principle, someone could maybe search for the "lost records" and reassemble them by hand, I suppose. The 4 GB in the database would all fit on a data DVD, so maybe Max could burn one and let some volunteer give it a shot... or not! Any takers?

Many db systems include a "compact" utility - of the sort that your email db uses. When a db record is "deleted," the record usually stays in the db file, and only its link from the "record list" is deleted. Commpacting your email is how you DELETE all the "unlinked records" from the database file. SOME databases may include "recovery" or search utilities that let you save the orphans to a separate place???? If the unlinked records include the thread name and a date/time, a volunteer might sort out where they go so that an "errata thread" could post them back??????

All kinds of possiblilities - but what's practical? Probably just what we're doing - talk about it 'til Max and the clones get as much of it fixed as they can.

John