Actually there is a pattern, but not what you would expect. It seems even the makers of FTM differentiate between the sexes. Here's what I have noticed (and it works every time). Dad marries twice and has children with both wives. You select wife #1 as the "preferred" marriage. You add children for wife #1 - go to their tree page, then click on the "parent" tab and you are taken back to the preferred marriage. No problem. Then you add children for wife #2. Here's where it get s interesting. I have observed that IF the child is a son (male), when you click on the "parent" tab you are taken back to the correct family, Dad married to Wife #2. Now, if the child is a daughter (female), when you click on the "parent" tab you are taken back to her DAD's page, which will show the "preferred" marriage (i.e. Wife #1). That is where you are seeing the inconsistency. The solution is, while you are adding children to wife #2, temporarily make that marriage the "preferred" marriage. The parent tab will then always take you back to the right mother. After you are done, you can easily switch the "preferred" marriage back to wife #1. It just shows that even in FTM, daughters are "Daddy's little girl" :). Lorraine, in Kingston BJ wrote: Thank you for your comments. I am able to replicate this first problem but only erratically. Sometimes it returns me to the actual parents but at other times it returns me to the Preferred Spousal relationship. I have not been able to determine a pattern to this. I think what is happening is: * when you go to the child level - most times you are returned to the actual parents because the backward link is still in the temporary storage location. * when you go down an additional generational level and you attempt to return up two generational levels, you are returned to the preferred spousal relationship. I suspect the temporary memory storage was over written by the parents of the child and when you attempt to return to the grandparents, it must use the information from the relationship index which points to the preferred spouse. BJ

Thanks Lorraine and BJ for doing the "legwork" to define the conditions. I knew it wasn't random but clearly a programming issue of some sort. I just didn't have the time to pursue it as I was recovering and updating the database before I totally forgot what I'd been up to. Yes, I realize the "preferred" can be changed temporarily. I was doing updates mostly across a generation in a broad family line, so it wasn't practical - but that also probably masked the conditions to some extent. Do you know what the current link might be to report issues? J.Hintz On 1/29/2014 10:46 AM, Derk & Lorraine Sherren wrote: > Actually there is a pattern, but not what you would expect. It seems even > the makers of FTM differentiate between the sexes. Here's what I have > noticed (and it works every time). > > Dad marries twice and has children with both wives. You select wife #1 as > the "preferred" marriage. You add children for wife #1 - go to their tree > page, then click on the "parent" tab and you are taken back to the preferred > marriage. No problem. Then you add children for wife #2. Here's where it get > s interesting. I have observed that IF the child is a son (male), when you > click on the "parent" tab you are taken back to the correct family, Dad > married to Wife #2. Now, if the child is a daughter (female), when you click > on the "parent" tab you are taken back to her DAD's page, which will show > the "preferred" marriage (i.e. Wife #1). That is where you are seeing the > inconsistency. The solution is, while you are adding children to wife #2, > temporarily make that marriage the "preferred" marriage. The parent tab will > then always take you back to the right mother. After you are done, you can > easily switch the "preferred" marriage back to wife #1. It just shows that > even in FTM, daughters are "Daddy's little girl" :). > > Lorraine, in Kingston > > BJ wrote: > > Thank you for your comments. > > I am able to replicate this first problem but only erratically. > Sometimes it returns me to the actual parents but at other times it > returns me to the Preferred Spousal relationship. I have not been able > to determine a pattern to this. I think what is happening is: > > * when you go to the child level - most times you are returned to the > actual parents because the backward link is still in the temporary > storage location. > * when you go down an additional generational level and you attempt to > return up two generational levels, you are returned to the preferred > spousal relationship. I suspect the temporary memory storage was > over written by the parents of the child and when you attempt to > return to the grandparents, it must use the information from the > relationship index which points to the preferred spouse. > > BJ > > ********************************** > List information page > http://lists.rootsweb.com/index/other/Software/FTM-TECH.html > > Version 2008 - 2012 > http://ancestry.custhelp.com/app/home > ------------------------------- > To unsubscribe from the list, please send an email to [email protected] with the word 'unsubscribe' without the quotes in the subject and the body of the message > >