First, this is just FYI - I'm not looking for solutions for these, but just comments in case others run into the same. 1. One is just an annoyance. When updating a series of children in a family of a husband with multiple wives and children with each, I was also going back to the parents of the children by using the tab above the wife. When working with the series under the non-preferred wife, the correct parents are displayed on the tab, but when selecting the tab to return to those parents, the return is to the husband/father with the preferred wife. I assume anyone can recreate this. No data damage, just an incorrect use of the "preferred" flag resulting in some extra navigation required by the user. 2. The other is a damaged database that could not be recovered. I tried the usual recovery methods and talked to Ancestry/FTM; no additional suggestions there. Database activity before the problem was not unusual. I was updating about 25 children at the bottom of their chains - adding a few, inserting middle names, adding/changing birth dates and places. A few place corrections also triggered 'fixes' to 3 or 4 other entries. Similar changes were made to parents and a few marriage dates added. Updates and notes were added to several grandparents. There were no unusual errors - nags when I 'fat-finger' dates or start to enter a place name in the date field. After adding an individual, I realized I was unable to find her in the index. Not out of sequence; she was not there at all. So I went off to compact the file. That appeared to start normally, but failed soon with the "FTM 2014 has stopped working" panel and a forced close. Any attempts to open the file again results in the same. The usual 'back door' merge to a new file with one entry fails with a new message - "database disk image is malformed". Browsing tech sites for the message seems to indicate others may sometimes be able to recover if they have an SQL data dump feature in their software kit so they can dump and reload their database. It would appear that a database update failed and the compact feature not only couldn't recover it, but it couldn't just drop that update and process the remainder of the database. It may have no relation to the out-of-sequence index some people have experienced. The failure to process an index entry at all could just be the symptom I saw. FTM was not reinstalled as it worked normally with other databases. I went to a backup and was only missing a couple of small updates in addition to this batch ... and the update list was on paper that I had not yet shredded (bonus!). [Using Win/7, 64-bit, database only about 11,000 people.] J.Hintz