I did get a reply from their support folks. They gave me some options to test -- to include creating a temporary tree from scratch and go through the manipulations with the tree to see if I could re-create the hangs. It didn't. So the assumption is that it's in the database itself, so the next step is to (paraphrasing and condensing) export everything, blow it away, then re-import. I haven't had the time (busy at work and home) to try this yet. I definitely will prepare a full report (well, a "Reader's Digest" version) for everyone here when I'm done. Gimmie another week...
Adding to your rant: I couldn't agree more on the lack of data/diagnostic tools. One of the reasons I got the FTM software was to be able to easily correct data errors -- and all it's done was to assist in creation of multiple copies of the *same* events on folks, duplicate people, and generally make my experience one of drudgery and monotony as I slugg through deleting duplicates. I work with databases at my job, it's not that hard to automagically find and remove exact duplicates of data... You'd think they'd welcome users cleaning up their own stuff -- imagine the wasted terabytes of storage they are using to keep "bad data" -- like when I discover a mistaken added person in my tree and delete them -- and it *keeps* all the others above them ("no direct relationship found") so I have to go in an manually remove each one; that's ludicrous.
Adding to your rant: I couldn't agree more on the lack of data/diagnostic tools. One of the reasons I got the FTM software was to be able to easily correct data errors -- and all it's done was to assist in creation of multiple copies of the *same* events on folks, duplicate people, and generally make my experience one of drudgery and monotony as I slugg through deleting duplicates. I work with databases at my job, it's not that hard to automagically find and remove exact duplicates of data... You'd think they'd welcome users cleaning up their own stuff -- imagine the wasted terabytes of storage they are using to keep "bad data" -- like when I discover a mistaken added person in my tree and delete them -- and it *keeps* all the others above them ("no direct relationship found") so I have to go in an manually remove each one; that's ludicrous.