Family Historian User Group

Thank you, I took the precaution of checking the 'Wish Lists' first but obviously not well enough. I have since reviewed & voted.

Thanks for your prompt response. I have done that already as a temporary fix. The problem is that Factowner alone sorts on given name whereas the Fieldtext sorts in Surname, which I find more usable. When I have both fields & cover the 'Factowner' so that only the initial 'box' shows, when printed t...

I have found it necessary to write a number of 'Fact' type custom queries (to highlight to trace missing information) & have used the '=FieldText(FactOwner(%FACT%,1,MALES_FIRST),'INDI.NAME:SURNAME_FIRST')' with success. It would be nice if this expression could have the same ability as the '%INDI%' ...

I would appreciate a data validation feature in addition to the existing validation, which appears to be a GEDCOM validation. Mis typing has sometimes left me with individuals who died at 250 years old, were married before being born, whose children were born before their parents, etc. I note in the...

Doing Australian family history a proportion involves convicts & their transportation. I find some difficulty in Family Historian in this area. 1) I have tried to set up a fact for convict but cannot figure how to capture all the info needed eg {indi} was convicted of {offence} at {place} on {date} ...

When I have date phrases I find that they do not display in diagrams or report in queries. Is there any reason (of action that I'm missing)? Date phrases sneek in by accident due to mis-typing & are otherwise hard to find or I use them intentionally to separate guesses from Genuine then have multipl...

In some circumstances it is of assistance to record (& report, diagrams etc) that an individual was 'never married' (& will never be, ie after their death) or that a couple had 'no issue'. Recording this info would prevent ones self (or others), at a later stage, from repeating a futile search.  A '...

Good thought(s) (which I hadn't considered). It might be possible the feature on single line fields. But I recognize that there is a 'consistency' issue for the 'look & feel', but it would be nice.

Using the same .GED data file the Ahnenblat program finds more legit. validation problems than FHv4.  Is there scope to increase the validation checks to include obvious mis-typing errors such as: Birth of child before mother/father, age differences between siblings of greater than x years, age diff...

Is there any reason why data entry could not be completed with or exited (&saved) using the arrow keys to progress to the next field (in the arrow direction)?  While exiting using tab is a legit. option, as a keyboard based data-entry it seems strange to not be able to exit using the above methods. ...

Is there a function available for a 'Fact' type custom query which will display the fact owner(s) with surname first (preferably in upper case) followed by given names (in normal order)?

ID:4134