Pushed a button I should’na pushed.
Me mum’s entire line from great-great gran went blooie. Vanished. Especially nuisanceful is losing the line in your DNA record…and this one carries my MtDNA.

One of the good things about Family Tree software (Ancestry.com) is that gone is not gone, if you can find the thread.
Thirty minutes of searching (the descendants of Eliphalet Maxwell are occasionally confused) turned up the critical Eliphalet (you would not believe there was more than one person in Massachusetts named Eliphalet, but there was, and one ancestress may have been married to two of them…still have to straighten that out!) —and I got it. Blink! There they are all back again.

I hate it when that happens. Family Tree is good at finding duplicate ancestors, ie people you’re related to more than once, or three or four times,—which can save you a LOT of copying (x-great-grandfather Thomas Wilson appears twice, with ALL his predecessors, and the same wife with all of hers) but if you run that utility and merge two people who shouldn’t be merged, because (thanks to the Julian/Gregorian calendar mess) you frequently have a person being born in 1722 and 1723. And the fact that parish records often take April as the first month of the new year just makes everything lovelier still, in terms of Are these two people the same person? So when the program asks if Eliphalet born in x year is the same Eliphalet born in x plus or minus a year—and you say ‘yes’, you can end up copying one record over another and just making a mess.

Caution, Will Robinson.

And don’t panic. Nothing gets erased—just…disconnected. And you have to find the button and buttonhole.