For the past few years I have a big note in my FTM file of record (sadly) saying not to trust this file. I had numerous cases of the No Spouse Entered bug. See: https://www.google.com/#q=ancestry+no+spouse+entered+bug As most of the data and features seemed to work, yet on occasion I'd end up in a navigation dead end on a person only in the data once, yet could navigate through a non-dead end if I came upon that individual from a different direction. Someone in Australia (I think) volunteered to look at one of my corrupted data files, and he concluded it was damaged beyond all repair and could not even guess how it had happened. I think it happened when some bad merges were done. That they didn't go well wasn't realized at first, so the files got saved as my only "good" copy eventually. I tried exporting/importing as GEDCOM and it persisted. So... I thought it was still in my file. So a few days ago I started a little project to begin writing a little program to parse and lint check GEDCOMs. I was happily making progress when I discovered that some name look ups returned null strings for some spouses. I looked in the FTM Mac 3 program at the individual, and sure enough I saw the [No Spouse Entered] string! At that point it was good and bad news. Good that I now had a simple tool to find them, bad in that in my file of a little over 2000 individuals I found 46 such entries! I started reading on how to fix the problem (see google search above) and it amounts to finding, detaching, and a few handstands while shaking your right foot in the air. Maybe. So I went back to the FTM program and poked and prodded a bit. It used to be that when you added a spouse when that dreaded string was found, it was retained as a bogus spouse. I tried adding a spouse. It behaved. The new spouse appeared, the No Spouse Entered disappeared, and the spouse count was correct, not incremented. So... it seems that No Spouse Entered is now no longer a bug or a problem. Can someone confirm that for me? And if it is now not a problem in FTM Mac 3 (and latest Windows Version) did having it once be a bug harm my data in any way? I am hoping not. In which case I can trust my data file again. And I'd like my day and a half back of programming to parse GEDCOMs. (Although I think it may develop into a solution for what I will request from Ancestry FTM programmers in my next message). Thanks, John