=Relationship() function - consistent output

GladToBeGrey · Post by **GladToBeGrey** » 16 Dec 2008 10:57

The =Relationship() function returns inconsistent results when the TEXT parameter is employed.

Some 1st Cousins are listed simply as 'cousin', whereas 'removed' cousins are listed as '1st cousin [number] removed'. It would be better if all 1st cousins were so identified, or there were an optional parameter to select this behaviour.

Similarly, 'once-removed' versus 'twice removed', three times removed' etc. Remove (sorry!) the additional hyphen.

Given the lack of any conditional processing, consistency of output makes it easier to develop queries based on the function results (this is a more general observation).

http://www.fhug.org.uk/wishlist/wldispl ... lwlref=416

ID:3160

PeterR · Post by **PeterR** » 14 May 2009 14:50

Currently (FH v4.0.1) it appears that 'once-removed' is hyphenated only for 1st cousins. I agree that more consistency would be an improvement, although personally I'm not bothered that just 'cousin' is used for '1st cousin'.

YouTube · Post by **Jane** » 14 May 2009 15:30

Personally I prefer 'Cousins' where they are 1st cousins as it's the common usage of the term. My cousins are my Dad's sisters children.

If you are using the results in queries why not use the value version results, rather than the human readable?

ChrisBowyer · Post by **ChrisBowyer** » 17 May 2009 07:55

I happened to notice in Tribal Pages, it says things like 'grandfather's second cousin', which I think is much nicer than the ...removed notation, and less ambiguous ('removed' gives no clue as to the direction).

Family Historian User Group