As the wife of my 27th GGF and the mother of my 26th GGM, she is my 27th GGM.
BUT, as daughter of my 25th GGF and 25th GGM, Legacy wants to make her my 24th SOMETHING, and it picks 24th GGA rather than 24th GGM. 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. It gets even messier when such a couple has two children that are also direct ancestors. Legacy knows she is a direct ancestor because she is Ancestor Colored and Direct Line bolded as such. It is the problem not allowing her to be named as a GGM when the degree of relationship conflicts with that of her husband and daughter. The program does not allow for such complications, which is odd for a genealogical program. It's in the math. Too bad. Some acknowledgement of this limitation needs to be made. CE -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Tuesday, December 15, 2009 2:30 PM To: [email protected] Subject: RE: [LegacyUG] Relationships Incorrect As a matter of interest, what relationship would you expect to see? I'd have thought that the sister of your nth GGF would show as your nth GGA, that being her state at time of birth. (but then again I've been wrong before and I'm sure I'll be wrong again!). Bill -----Original Message----- From: [email protected] [mailto:[email protected]] Sent: Tuesday, December 15, 2009 10:20 PM To: [email protected] 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
