Family Historian User Group

Thanks again Mike.

I think she will continue as she has always done - I saw the 'Associations' tab example and it just occurred to me that it would be possible to create what I wanted.

Can't win them all

Hi Mike & Helen Many thanks for your responses. Why am I trying to re-invent the wheel? - Focus View does it all. My wife dislikes Focus View and never uses it - and that's from when we first started with FH (v2 I think). She works solely in the Records Window and the Properties Box. So I thought th...

Hi Folks I am also trying to customise a Property Box Tab but appear to have found something that I can't do. What I am trying to create is a tab showing immediate relatives of the individual. e.g. Father, Mother, Sibling 1, Sibling 2... Child 1, Child 2... I've tried %INDI.FAMC[1]>HUSB[1]>NAME[1]% ...

Mark I am not suggesting that because a group of people are in a household list they should automatically be added to a family. The household list merely serves as a starting point to verify their relationship, if any. This is no different from any other census. The only piece of real information th...

One of the benefits of being retired

You're welcome.
So far I've managed to locate nearly 400 relatives, and 90 of them I didn't have before

Hi I think that all of the entries returned have a Louisa on their page. If you look at the image below you will see that I have sorted out each of the families. Apart from the family headed by Ellen Davies I have resolved all the Louisas. 1921 Search.jpg In this case I would re-try the process usin...

Another tip to find the other household members. Once you've found a person in the correct household: Note the name of the person you've found USE NAME AS DISPLAYED, not what it should be Note the 'Parish' and 'Registration District' Click on 'Advanced Search' at the bottom of the page On the 'Adva...

Hi Michael Many thanks for the image, I can now see what you mean. 1. Open FH with Focus window & Property box showing as per your image. 2. Click the Gear Wheel at top right and select Options Image 0.jpg 3. Set 'Preferred Position for Citation List Pane' to 'Open in New Window', twice Image 1.jpg ...

Hi Michael

Like you I am running Windows 10 under Parallels 17 on my iMac with Monterey.

Did you try the tweaks that I suggested?

Are you running Windows in coherence mode?

Dave

Hi Michael If I'm understanding you correctly, you want the Citation List Pane (the one with the yellow background) floating. The following works in FH7 on Windows 10 (I'm still running FH6 on Windows 11) At the top right of the Properties Box is a Gear Wheel. Click on that and select Options You wi...

Hi Mike The actual example I gave was 1 year out on the MAX, the same principle as the one you gave: However, if we use a date range for Birth and Death it fails on MAX e.g. DOB btw 1918 and 1922 [Earliest date is 01/01/1918; Latest date is 31/12/1922] DOD btw 2016 and 2017 [Earliest date is 01/01/2...

Latest update from CP I obviously got a day adrift in the example that I submitted :-( However, they accept that there is still an issue. If the earliest possible birth date was 1/1/1918 and the latest possible death date was 31/12/2017, then the maximum possible age would be 99, would it not? I.e. ...

My parade was quite wet enough without you raining on it

I've replied to CP and given them a worked example showing that btw fails on MAX

I've just tested the new implementation of =EstimatedAgeAt() and it now gives the expected results.

Prior to this update it returned (for a particular individual) 47 for both MIN and MAX whereas it should have returned 46 for MIN and 47 for MAX.

This is now working correctly

Just heard from CP that in the next release 7.0.9.0 they have fixed 'Estimated Age At'

The “EstimatedAgeAt” built-in function was not returning the min and max values that users might reasonably expect. This has been fixed.

Thanks Mike, i hadn't thought about leap years and 1752.

Following on from the above, there appears to be other flaws with dates.

If we use =DayNumber(DateAt(1940,0,0)) I get a value of 708207

Then if we use =CalcDate(DateAt(1,1,1),0,0,708207) I get 22 Dec 1939


Mmmmm

Just had a reply from CP - partial success. They have clarified why it doesn't work - it appears that MIN/MAX is only applied to the Birth Dates. It also implies that a year is being taken as a whole value, with no discrimination e.g. A person born on 16th May 1910 is taken as exact, but when compar...

I've had a further email from CP asking me to Please send us a quote for the description which you believe to be incorrect . I have done this along with a worked example showing how the =EstimatedAgeAt() function is operating. To my way of thinking it is straight forward:- DOB: 06/02/1879 DOM: 1926 ...

I've gone back to CP and reiterated the issue regarding =EstimatedAgeAt() . I also pointed out that whilst I possibly could, as they suggest, write a Plugin to emulate {age range} , that a) I don't really want to reinvent the wheel, and b) if it's in a Plugin it won't be available in a query which i...

Mike, Sorry about the Wish List posting - I hadn't noticed your post when I looked through the titles.

In FH {age range} is available for use in sentences but is not available as a standalone function.
This is used to display the expected age in brackets when entering a new event
Spoke to Calico Pie (Nov 2021) and they suggested adding it the wish list.

I agree, it is not possible to really come up with suitable values for Before and After. I've had a response from CP. They appear to have ignored the =EstimatedAgeAt() comments. And no, they won't let me have the algorithm for the {age range} To: Dave Simpson >> Would it be possible to have the algo...

I have contacted CP regarding =EstimatedAgeAt() , at the same time I asked if they could let me have the algorithm for {age range} . A little experimenting leads me to believe that it may be how FH interprets dates when they are not fully qualified. It appears to me that all such dates are interpret...