I might agree about the male thing except that it is ONLY when the degrees don't jibe that this occurs. For some reason, Legacy will not allow her to be called my 24th GGM if she is married to my 27th GGF and mother of my 26th GGM.
Sherry told me once that the program SHOULD show her as my GGM if I limit Blood Relationships to the closest one. After all, she IS my direct ancestor. Unfortunately, it doesn't. CE -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Tuesday, December 15, 2009 3:20 PM To: [email protected] Subject: Re: [LegacyUG] Relationships Incorrect Are each of the various 'numbers' accurate, if not the one you would guess is the 'first' choice; Check out Relationship Calculator to get the many multiple pathways. You are related to my kids, so I deal witht the same stuff. It seems the calculation is 'male' checking first and this has been discussed in the archives. My kids have Charlemange as a grandparent on over 60 paths, which may leave out some multiple lines.My guess is that the programmers used the 'legal' rules for inheritance, and some fixes were done last year. Rich in LA CA ----- Original Message ---- From: "[email protected]" <[email protected]> To: [email protected] Sent: Tue, December 15, 2009 2:20:23 PM Subject: [LegacyUG] Relationships Incorrect I have a 25th GGFather and GGMother with two children, Ralph & Cecily. Ralph and Cecily are each direct ancestors of mine. This is shown correctly in Legacy by Ancestor Color Coding and by Direct Line bolding. Ralph is shown as my 24th GGF, married to my 24th GGMother. BUT, Cecily is shown as my 24th GGAunt, married to my 27th GGFather. So I guess Legacy can't figure out what to call my relationship to Cecily, even though it knows she is a direct ancestor, as evidenced by the correct Color Coding and Direct Line bolding. So Relationship Calculator is useless for me, because it is not only the far distant ancestors where this occurs; those are just easier to find in my database. Is NAMING the correct relationship just too complicated for Legacy? Is there no way this can be fixed? If this cannot be fixed, PLEASE advise us users accordingly. CE Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.5.427 / Virus Database: 270.14.101/2555 - Release Date: 12/14/09 19:40:00 Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
