* Calculated death date
Calculated death date
Sorry, I'm having a meltdown!
If I do not know the date of death, how can I show that i.e. if over 110 years old they have died?
If I do not know the date of death, how can I show that i.e. if over 110 years old they have died?
Derek
Windows 10
Search Engine - Chrome
Windows 10
Search Engine - Chrome
- paultt
- Famous
- Posts: 114
- Joined: 18 Jan 2005 21:59
- Family Historian: V7
- Location: Hampshire, England
- Contact:
Re: Calculated death date
Tools_>Preferences->Estimates
- tatewise
- Megastar
- Posts: 27082
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Calculated death date
I'm not sure I understand the question ~ show where for what purpose?
It is not clear how the Tools > Preferences > Estimates answers the question.
=EstimatedAgeAt( %INDI%, Today(), MIN ) will return a person's age today.
If that is greater than say 110 then they can be assumed to have died.
The value in Tools > Preferences > Estimates is irrelevant.
The =EstimatedDeathDate function uses that value but you then have to compare that Date with =Today().
It is not clear how the Tools > Preferences > Estimates answers the question.
=EstimatedAgeAt( %INDI%, Today(), MIN ) will return a person's age today.
If that is greater than say 110 then they can be assumed to have died.
The value in Tools > Preferences > Estimates is irrelevant.
The =EstimatedDeathDate function uses that value but you then have to compare that Date with =Today().
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
Re: Calculated death date
Mike,
I'm trying to sort out a number of "inconsistency issues" that have been identified by My Heritage. I'm new to My Heritage and hadn't realised that if I do not put a death date into my FH programme, over 110 years of age shows an "inconsistency,
Not come across this before, I assumed (!) all ged files assumed death if over a certain age?
I'm trying to sort out a number of "inconsistency issues" that have been identified by My Heritage. I'm new to My Heritage and hadn't realised that if I do not put a death date into my FH programme, over 110 years of age shows an "inconsistency,
Not come across this before, I assumed (!) all ged files assumed death if over a certain age?
Derek
Windows 10
Search Engine - Chrome
Windows 10
Search Engine - Chrome
- tatewise
- Megastar
- Posts: 27082
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Re: Calculated death date
There is no assumption of Death inherent in GEDCOM files. That is all up to the genealogy product and you the user.
So you need to run an Individual Query with =EstimatedAgeAt( %INDI%, Today(), MIN ) as a Column.
Then you can sort that Column in the Results Set to identify aged people and give them a Death Event.
I suspect MyHeritage only needs the event without a Date but if a Date is needed then use Before 1234 where 1234 is say 110 years after their Birth.
So you need to run an Individual Query with =EstimatedAgeAt( %INDI%, Today(), MIN ) as a Column.
Then you can sort that Column in the Results Set to identify aged people and give them a Death Event.
I suspect MyHeritage only needs the event without a Date but if a Date is needed then use Before 1234 where 1234 is say 110 years after their Birth.
Mike Tate ~ researching the Tate and Scott family history ~ tatewise ancestry
Re: Calculated death date
Mike,
Many thanks - I may just take this up with My Heritage - I certainly like the idea of them pointing out errors, but this may be a little extreme?
Food for thought!
Many thanks - I may just take this up with My Heritage - I certainly like the idea of them pointing out errors, but this may be a little extreme?
Food for thought!
Derek
Windows 10
Search Engine - Chrome
Windows 10
Search Engine - Chrome