In the tree, they occur in the following order: pair 1 first person, pair 1 second person, pair 2 first person, pair 2 second person. Pair 1 first person has *no* indication that this is a duplicate line. Pair 1 second person states that it is a duplicate line and points to the correct page for pair 1 first person. *However*, pair 2 *first* person states that it is a duplicate line, but incorrectly points to the page for *pair 1 first person*. And pair 2 second person has no indication that it is a duplicate line. There is no correct pointer either direction for pair 2.
Ruth Ann
Karen Sipe wrote:
Mike, thanks for bringing this up. I too have a cousin line but fortunately the second person in the family descent doesn't have second or third marriages. It did bring to me another problem with the same situation.
The first Person in the report gets a number indicating that they will be reported again in the report but the second person has no number which seems to indicate he may not have had family. This is compounded in the report when the couple is listed with their children because again he has no number. It does list his parents but with a large report that means index searches or tedious reading. I think he should have his own number and certainly as you pointed out any further marriages need to be somewhere. Karen V. Sipe
From: "koshka" <[EMAIL PROTECTED]>
Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp
To find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/
To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp
