I just read your posting with great alarm. I was searching ancestry for "corruption" because of a problem I have just had. I am a long term Legacy Family tree user and Ancestry subscriber. Although I like Legacy with the Treesync feature of FTM I decided to switch to FTM2012. FTM2012 supposedly reads Legacy files directly so I imported my file (no errors reported) and off I went. Fortunately my suspicions were aroused after a only couple of days of inputting. FTM2012 had screwed up my data. Further examination of the problem showed that although the number of individuals recorded by FTM was the same as Legacy, the number of families had been reduced with relationships made that are pure fiction. FTM gave a childless person from the early 1900s a child born in 1813. And others too. I wonder how many customers have switched to FTM from Legacy, read in their file and not noticed yet? If there is anything worse than data corruption (which is bad enough) it is silent data corruption. I am appalled.
↧