Search for content in message boards

FTM2012 Corrupting Data Today Worse than when Problems Reported 13 Months Ago

Replies: 32

Re: FTM2012 Corrupting Data Today Worse than when Problems Reported 13 Months Ago

Posted: 28 Feb 2013 10:31AM GMT
Classification: Query
It is beyond me why, when "children not in birth order" is considered a DATA ERROR, FTM does not default to putting them that way or provide a way to globally correct; or at least provide an option "put all children in birth order."

Uncheck the box on the options list of the error report and it will no longer search for births out of order. I do this even though I consider it an error when they are out of order. The reason I uncheck the box is because FTM is forever [unilateraly] changing the birth order. I am leaving them alone in anticipation FTM will someday fix this
SubjectAuthorDate Posted
susandallri 2 Mar 2013 2:33PM GMT 
ghenning 3 Mar 2013 5:38AM GMT 
susandallri 3 Mar 2013 3:46PM GMT 
ghenning 27 Feb 2013 5:18AM GMT 
Glenn Harvey 28 Feb 2013 1:39AM GMT 
barbarajfn 28 Feb 2013 4:44PM GMT 
KATHYMARIEANN 28 Feb 2013 5:31PM GMT 
gldaggett 25 Jan 2013 5:30PM GMT 
lbragg 26 Jan 2013 7:52PM GMT 
janeposkitt 28 Jan 2013 4:30PM GMT 
per page

Find a board about a specific topic

  • Visit our other sites:

© 1997-2014 Ancestry.com | Corporate Information | Privacy | Terms and Conditions