* ageat and =ageat question

Homeless Posts from the old forum system
Locked
avatar
justone
Diamond
Posts: 82
Joined: 05 Mar 2006 14:42
Family Historian: None

ageat and =ageat question

Post by justone » 17 Dec 2006 18:10

Likely was asked before, but I wasn't able to locate the thread in here.

Referring to the help in section 'understanding functions' is says.

> Functions and other expressions can be used in Queries, Diagrams and Reports.

somwhere else it says

> e.g. ['...') .... you cannot however do this in diagrams or reports.

Hmm now I'm confused.
A function does need an input I'd say otherwise a function isn't of much use.

What I tried to archive is to have the age of mother and father displayed in individual boxes, but without any luck.
No matter if trying with a leading '=' or not.

Any idea if that's possible at all ? Even if using some weird templating ?

thanks in advance

ID:2034

User avatar
Jane
Site Admin
Posts: 8442
Joined: 01 Nov 2002 15:00
Family Historian: V7
Location: Somerset, England
Contact:

ageat and =ageat question

Post by Jane » 17 Dec 2006 20:15

You would need to provide a date to have an age at.

You say the age of the Father and Mother at what date did you want the age?

avatar
justone
Diamond
Posts: 82
Joined: 05 Mar 2006 14:42
Family Historian: None

ageat and =ageat question

Post by justone » 18 Dec 2006 11:21

Hi Jane, played with the new EstimatedAgeAt function.

But it suffers the very same problem the solution below runs into.

Iused
=AgeAt(%INDI.~FATH>%,%INDI.BIRT.DATE%)
=AgeAt(%INDI.~MOTH>%,%INDI.BIRT.DATE%)
=AgeAt(%INDI.~FATH>%,%INDI.FAMS>MARR.DATE%) =AgeAt(%INDI.~MOTH>%,%INDI.FAMS>MARR.DATE%)
to get age of father and mother, both at birth and marriage.

And I also get ages displayed which are past the real death of a person. I think I'll still have to wait until Simon implements conditions.
eg. if =ageat(death,event) > 0 then =ageat(birth,event)

Or someone being aware of any complexed scripting to deliver something like that ?

User avatar
Jane
Site Admin
Posts: 8442
Joined: 01 Nov 2002 15:00
Family Historian: V7
Location: Somerset, England
Contact:

ageat and =ageat question

Post by Jane » 18 Dec 2006 11:38

When it says input, that is an entered parameter, the box which pops up to allow the information to be entered in Queries.

There are no pop up entry options when running reports or diagrams so the parameters must be accessible fields.

The ageat parameter really just returns what the age would be at a date, and does not take into account any entered death date.

avatar
justone
Diamond
Posts: 82
Joined: 05 Mar 2006 14:42
Family Historian: None

ageat and =ageat question

Post by justone » 19 Dec 2006 11:28

Thanks Jane got that .... works as designed.

While at dates ....
why does FH display [F] 13.1.0012 when entering a french date being 13.vendemaire of year 12 ?

As far as I know vendemaire is september thus it's month 9 not 1.
Any idea if that's bug, or does FH count the months in a way that january isn't month 1 of each year ?

avatar
PatrickT
Diamond
Posts: 86
Joined: 08 Apr 2006 13:46
Family Historian: V6.2

ageat and =ageat question

Post by PatrickT » 19 Dec 2006 11:42

It's probably because Vendemiaire was the first month in the French Revolutionary calendar

avatar
justone
Diamond
Posts: 82
Joined: 05 Mar 2006 14:42
Family Historian: None

ageat and =ageat question

Post by justone » 19 Dec 2006 21:02

@PatrikT >It's probably because Vendemiaire was the first month in the French Revolutionary calendar

Yep, you're right as long as you define dates within the first year only.

Wikipedia tells the following:
It started 1789
This first years was 5 1/2 months in length only, since Jan 1st 1790 was day one of year 2.
But even this was reverted somewhat later so know I relly could imagine why this calender didn't last for that long ;-) It was that complicated I bet most living at that time were happy to make their living, not bothing too much about calenders.

Locked