Search for content in message boards

A problem with dates.

A problem with dates.

Posted: 28 Apr 2013 8:33PM GMT
Classification: Query
Hi, I am having a slight problem with dates. I am using FTM2012, on Windows 7. My database has a total of 4323 records. Some of my records were originally entered in Brothers Keeper, some in Family Origins for Window(Parsons), some in FTM2011 and some in FTM2012. To explain what I am seeing, first I open the People View, and filter in all records where the death date is blank, resulting in 80 records(way too few), then I filter in all records where the death date is NOT blank, resulting in a total of 1262 records, not 4323!! When I look at the 80 blank type records, all of them have no date information, but the place information does contains data. The second thing I am seeing, I make a custom report that contains all records and export it to a .csv and open it in Excel. A date that displays in FTM2012 as 08 Apr 1949 will display correctly in Excel as 8-Apr-1949(or chosen format). A date of 08 Apr 1849(Being before 1900 is key here, I think) will display as a string value=08 Apr 1849. when sorted A->Z all the pre 1900 dates appear incorrectly, AFTER the post 1900 dates followed by all the blank dates. When I format the cells in Excel as numeric, I see that all dates for 1/1/1900 up to today are numeric, and everything before 1900 are string values, like "08 Apr 1849". I have also exported to RF and PDF am seeing similar problems with the data.

So my questions are, does anyone else see the blank plus notblank = less then the total records? Does anyone else see their export to .csv have two different date formats? Is there a way to normalize all the date information in FTM? Do I need to uninstall/reinstall, and how does one normally do that?

Thanks for reading this way too long post.
Alan

Re: A problem with dates.

Posted: 28 Apr 2013 9:33PM GMT
Classification: Query
Alan, it looks like FTM 2012 has a problem with that filter. I have a tree that I have a copy in FTM2012 and a copy in FTM Mac 2. When I filter by blank death date in FTM2012, I get 10 records - all ten have a Death fact with a place or description, but no date (just like you're seeing). In FTM Mac 2, I get 923 records - the same ten, plus 913 others that don't have a death fact. This is a bug.

I will report the bug to support@ancestry.com & suggest you do the same.
Attachments:

Re: A problem with dates.

Posted: 28 Apr 2013 9:48PM GMT
Classification: Query
Do you have people without a Death Fact? If so, anything filtering on Death date won't be picked up.

See if this is the case by Filtering on Death > Any Data > Does not exist. This will list the people who don't have a death fact.

Re: A problem with dates.

Posted: 28 Apr 2013 9:57PM GMT
Classification: Query
In my case, Death > Any Data > Does not exist gets me the other 913 people, so it's a valid work-around. However since FTM 2012 and FTM Mac 2 are behaving differently on Death>Date>Is Blank, one of them has a bug (I guess it's up to Ancestry to decide how they want that filter to behave; personally I prefer the way Mac is doing it currently)

Re: A problem with dates.

Posted: 28 Apr 2013 10:07PM GMT
Classification: Query
Yes, Filtering on Death Any Data Exist, gets me the same number as blank plus not blank. And interestingly, filtering on Death Date Before 1/1/1900 plus Death Date After 1/1/1900 doesn't produce all the records either. It produces the same set as Death Date Is Not Blank, 1182 records.
per page

Find a board about a specific topic

  • Visit our other sites:

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