Family Historian User Group

It doesn't sound to me as if you're doing any wrong.  The problem is just that F.H. doesn't automatically remove duplicated information for you.  You can easily use the expansion buttons to hide duplicates (and use Override Text to add a comment to this effect if you want to).  We have had various r...

P.S. I should have added that File Stats sounds like a good idea; so why not add this to the FHUG Wish List.

I may have misunderstood the requirement, but why not just unlink the other spouse?   It may be that I have missed the point here.  Or even if I haven't, it could just be a convenience thing - if you're looking at X, why should you have to navigate to Y to do what you want to do?  Either way, by all...

The Total number of Individuals and Families is shown in the status bar (bottom right) when you are viewing the Records Window.   You can use a query to count records of any given type because when you run a query, the number of records in the result set is shown in the status bar.  So you could use...

P.S.  If you click on File > 'Split Tree Helper' that opens the Split Tree Helper dialog.  If you then press on the Help button, you will find a more detailed explanation of how to do exactly the kind of thing you are trying to do.

The best way of doing this is to find a query that gives you all the people you want.  For example, 'Relations and 5 Nearest Relationships' might do it perhaps (don't worry about the columns - each row returned represents a record and its these records that matter for current purposes).  If that que...

Lyn Jane asked me to have a look at this one. In most reports she would be right, but I don't think she is about the Family Group Sheet. At present I can't see any way that you can get the record id (family Id) into either the title, the page heading or the top section. That does seem something you ...

Suppose there were a filter mechanism on the Records Window that allowed records to be filtered (excluded or included) based on a query?  The query could be any kind of query.  It might, for example, be 'all descendants of everyone in Named List 'roots''.  When you executed the filter it would look ...

Hi It sounds as if you have entered the data correctly.  But it isn't a bug either.  If your wife's ggf appears in 2 families, first showing birth parents, and the second with adopting father, the program would be remiss if it didn't show (a) that your ggf's mother had 2 spouses, and (b) that your g...

Frank you are quite right that in All Relatives diagrams, half-siblings line up with cousins.  If you look at the last page of the Quick Start Tutorial you will find in the section on Relationship Descriptions an acknowledgement that 'they don't properly account for 'half' relatives'. Laying out 'Al...

How about just writing the page numbers on the back of each page in pencil as they come out of the printer?  That way you don't have to tipex them out again when you've got the whole thing assembled.  Just a thought.

Can you just confirm that the problem occurs when you are showing an 'All Relatives' diagram with you as the root.  You are not seeing your grandfather's first wife and children by his first wife?  Is that correct? Can you also confirm that you have recorded a parent (mother, father or both) for you...

Louise To get each person's first 3 marriages, showing spouse name and date for each marriage (i.e. 6 columns) you want the following 6 expressions: INDI.~SPOU[1]> INDI.FAMS[1]>MARR[1].DATE INDI.~SPOU[2]> INDI.FAMS[2]>MARR[1].DATE INDI.~SPOU[3]> INDI.FAMS[3]>MARR[1].DATE Looking at the expressions y...

Could you explain in a little more detail what symptoms you are getting?  You say: 'I have upgraded and next time I used FH notes very strange names appearing on diagrams. The names had no relation to the actual names, which were still correct on the data file (left click) but the text (right click)...

Peter I presume that the text scheme you are using is one that has (or can have) 5 or more lines.  A change was introduced with large text schemes, to get round a problem whereby large text schemes could sometimes get text chopped off at the top or bottom.  The fix was to make the text a little smal...

I take it that you're talking about the 'Relationship Description' that appears down the side diagrams.  As Jane says, if you use a text scheme, such as 'Names, Dates, How Related' which puts the relationship into the box, you should find that that gives the right result. The fact that Relationship ...

Can I just stress that the workaround of switching the sexes of people in a text editor, as described, is a workaround that we cannot guarantee is problem free.  F.H. was not designed to work that way; so it may cause unanticipated problems in the software. If you want to try it, please keep careful...

Thank you for that helpful information.  Sorry for the long delay in replying.  I have logged everything and will be investigating this further.

This sounds like a good candidate for a patch (patches are minor bug fix releases).  If we do one, we won't do it immediately but will wait a little while in case other bugs emerge which could be fixed in the same patch.

There is an ALIA tag and it does occur at level 1 within an Individual record, but it cannot be used to store a name.  It is used to store a link to another Individual record.  I don't recommend doing this but GEDCOM supports having multiple records for the same person, linked using the ALIA tag.  F...

I've looked into this but without so far locating the source of the problem.  Its tricky trying to determine what is happening with memory because Microsoft's internal memory manager will not necessarily free up allocated memory if it thinks there is no need to do so (i.e. if it thinks that you have...

Thank you for a very helpful description of how to reproduce the problem.  It is indeed a bug.  Investigation has shown that it only affects fields in the citation pane (the yellow area that you enter source citation details into). It will be fixed in 2.2.  Meanwhile as Jane says, the workaround is ...

Most software houses take the view that it is a mistake to give out dates for releases, that it causes more problems than it solves.  This is our view too (and our experience I would add).  I do appreciate that this can be frustrating for users though.  I can say that the intention had  been that 2....

P.S. I meant to say thank you to Michael for an unusually detailed and helpful account of the circumstances of the crash, which helped a lot when I was trying to reproduce it.

Following my previous email, I spent some time trying to reproduce the problem and have succeeded.  So please ignore the previous email, this is a definite bug in Family Historian.  Apart from the case mentioned in my previous email where you are working on a corrupt GEDCOM file, this is now the onl...