On the other hand, lower percentages of matches in the computer's eyes don't necessarily mean that the information IN the system is right. Under the 4 generation program, I submitted my paternal grandparents information as I was given it by family (who would've known, supposedly.) It's in the system, BUT as I got better with my research skills and got to BYU with ready access to films and things, I found out that the man that was thought by everybody in the family to be my great grandfather was really a STEP-great grandfather. Because information from Ancestral File was entered into NFS, my Grandmother shows up as the daughter of both her true father AND her step father. If we know things through documented data, fix them! The only One of Heavenly Father's children who will not occasionally make a mistake isn't walking among us here on earth right now on a regular basis. ALL the rest of us make mistakes, and SOME of them will show up in NFS. So fix them and move on, and try to not repeat the same mistakes. Karen In a message dated 5/8/2009 10:55:12 P.M. Central Daylight Time, john@ohanasoftware.com writes: Perhaps the reference to 84% accurate is actually referring to the % Match column in the IGI Search feature of PAF Insight or FamilyInsight. If so, then the person who said that the sealing can't be done is misunderstanding the % Match value. It is merely an evaluation of how closely the data in your PAF file matches the data found in the IGI. It does not mean that the person found in the IGI does or does not represent the same person you have in your file. That is something that is left to human judgement. And an 84% match is almost always representative of the same person. So, if indeed the 84% was the number that FamilyInsight or PAF Insight gave to the match, then it is very likely the correct person. In that case, ther e should be no hesitation in performing the sealing based on the information you found. Aloha, John ----- Original Message ----- From: "JACQUELINE KALINAUSKAS" <grandmajk6@msn.com> To: "FAMILY HISTORY WARD CONSULTANT" <lds-ward-consultant-l@rootsweb.com> Sent: Friday, May 08, 2009 5:35 PM Subject: [LDS-WC] HAVE A QUESTION PLEASE > > I have a member that did his fathers temple ordainces in 1991. He recently > went to the FHC to put his mom through temple > > ready (yes, we are not on nfs as yet) so he can get her work done and get > the parents sealed as well as have dad sealed to his parents. > > The problem is that the member was told that his deceased father shows in > temple ready only 84 percent accurate as the right person and therefore at > this point can not be sealed to his deceased wife or deceased parents. > Unfortunately the son (the member) doesn't have in his possession that he > can locate the proof that he did all the ordainces for his dad. > > So the question is , as the ward consultant, what and how do I direct this > brother ? Do I call family history support with the complete information > and see if they see something else or ask them to plug in the full & > correct information. At this point the family is left "hanging" so to > speak. > > Thanks in advance for some good answers from all of you experts. > > Jackie > > Please send the one word message SUBSCRIBE or UNSUBSCRIBE to > LDS-WARD-CONSULTANT-L-REQUEST@ROOTSWEB.COM > ------------------------------- > To unsubscribe from the list, please send an email to > LDS-WARD-CONSULTANT-request@rootsweb.com with the word 'unsubscribe' > without the quotes in the subject and the body of the message Please send the one word message SUBSCRIBE or UNSUBSCRIBE to LDS-WARD-CONSULTANT-L-REQUEST@ROOTSWEB.COM ------------------------------- To unsubscribe from the list, please send an email to LDS-WARD-CONSULTANT-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message **************A Good Credit Score is 700 or Above. See yours in just 2 easy steps! (http://pr.atwola.com/promoclk/100126575x1221823232x1201398636/aol?redir=http://www.freecreditreport.com/pm/default.aspx?sc=668072&hmpgID=62&bcd= May5909footerNO62)