From roots-in@roots-l.rootsweb.com Wed Jun 14 03:08:13 2006 Received: from mail.rootsweb.com (mail.rootsweb.com [192.168.65.34]) by admin.rootsweb.com (8.12.8/8.12.8) with ESMTP id k5E98Djb000845; Wed, 14 Jun 2006 03:08:13 -0600 Received: from roots-l.rootsweb.com (roots-l.rootsweb.com [66.43.16.22]) by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k5E98A8G022703 for ; Wed, 14 Jun 2006 03:08:10 -0600 Received: from roots-l.rootsweb.com (roots-l [127.0.0.1]) by roots-l.rootsweb.com (8.12.10/8.12.10) with ESMTP id k5E6WAFI016909 for ; Wed, 14 Jun 2006 02:32:11 -0400 Received: (from roots-in@localhost) by roots-l.rootsweb.com (8.12.10/8.12.8/Submit) id k5E6WATE016908 for roots-approved@rootsweb.com; Wed, 14 Jun 2006 02:32:10 -0400 Received: from lists5.rootsweb.com (lists5.rootsweb.com [66.43.27.41]) by roots-l.rootsweb.com (8.12.10/8.12.10) with SMTP id k5DGVtFI015315 for ; Tue, 13 Jun 2006 12:31:55 -0400 Received: (from slist@localhost) by lists5.rootsweb.com (8.12.8/8.12.8) id k5DJ7eDI013369 for roots-in@roots-l.rootsweb.com; Tue, 13 Jun 2006 13:07:40 -0600 X-Envelope-From: johnberryman@charter.net Tue Jun 13 13:07:40 2006 Received: from mail.rootsweb.com (mail.rootsweb.com [192.168.65.34]) by admin.rootsweb.com (8.12.8/8.12.8) with ESMTP id k5DJ7ejb013358 for ; Tue, 13 Jun 2006 13:07:40 -0600 Received: from mxsf22.cluster1.charter.net (mxsf22.cluster1.charter.net [209.225.28.222]) by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k5DJ7cEN011515 for ; Tue, 13 Jun 2006 13:07:39 -0600 Received: from mxip11a.cluster1.charter.net (mxip11a.cluster1.charter.net [209.225.28.141]) by mxsf22.cluster1.charter.net (8.12.11/8.12.11) with ESMTP id k5DJ7Xrf025088 for ; Tue, 13 Jun 2006 15:07:33 -0400 Received: from 66-168-49-52.dhcp.mdsn.wi.charter.com (HELO [66.168.49.52]) ([66.168.49.52]) by mxip11a.cluster1.charter.net with ESMTP; 13 Jun 2006 15:07:32 -0400 X-IronPort-AV: i="4.06,128,1149480000"; d="scan'208,217"; a="437868905:sNHT123252198" Message-ID: <448F0C79.2010009@charter.net> Date: Tue, 13 Jun 2006 14:05:29 -0500 From: John Berryman User-Agent: Mozilla Thunderbird 0.8 (Windows/20040913) X-Accept-Language: en-us, en MIME-Version: 1.0 To: joe2phil@drizzle.com CC: ROOTS-M@rootsweb.com Subject: Re: [ROOTS-L] AFN ? References: <448ED3C6.3070205@charter.net> <003501c68f13$9320f8c0$7b988843@y9w6c2> In-Reply-To: <003501c68f13$9320f8c0$7b988843@y9w6c2> Content-Type: text/plain; charset=windows-1252; format=flowed X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34 X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34 Sender: roots-in@roots-l.rootsweb.com There is a difference and I noted that when I came across it. It's the spelling of the last names. However, there is more than enough supporting data to show that these are the same people. I not had this happen a often but I have a few of these to deal with. The question is how do I deal with this in my records or who can I contact to clear this up? John joe2phil@drizzle.com wrote: >Hello John , I have been working the LDS stuff for many years , never have I seen the same person with 2 numbers ,there must be something radically different to get two numbers , What is it ???? , Phil >----- Original Message ----- >From: "John Berryman" >To: >Sent: Tuesday, June 13, 2006 8:03 AM >Subject: [ROOTS-L] AFN ? > > >>Good Day Listeners, >> >>I've a question for someone with more experience than I. I've a few cases where I've come up with more than one AFN for the same person. For now I've recored both. However, I'd like to know how you experienced people deal with this issue. I'd truly welcome any suggestions on this. >> >>Cheers, >>John in WI USA >>