From roots-in@roots-l.rootsweb.com Mon Jul 31 22:25:35 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 k714PZjb011042;
	Mon, 31 Jul 2006 22:25:35 -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 k714PX0P023775
	for <roots-approved@rootsweb.com>; Mon, 31 Jul 2006 22:25:33 -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 k711kkFI031176
	for <roots-approved@rootsweb.com>; Mon, 31 Jul 2006 21:46:46 -0400
Received: (from roots-in@localhost)
	by roots-l.rootsweb.com (8.12.10/8.12.8/Submit) id k711kkUA031175
	for roots-approved@rootsweb.com; Mon, 31 Jul 2006 21:46:46 -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 k6VKhUFI030518
	for <roots-in@roots-l.rootsweb.com>; Mon, 31 Jul 2006 16:43:30 -0400
Received: (from slist@localhost)
	by lists5.rootsweb.com (8.12.8/8.12.8) id k6VNM6sX027721
	for roots-in@roots-l.rootsweb.com; Mon, 31 Jul 2006 17:22:06 -0600
X-Envelope-From: JYoung6180@aol.com Mon Jul 31 17:22:06 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 k6VNM6jb027710
	for <ROOTS-M@lists5.rootsweb.com>; Mon, 31 Jul 2006 17:22:06 -0600
Received: from imo-m20.mx.aol.com (imo-m20.mx.aol.com [64.12.137.1])
	by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k6VNM38Z026260
	for <ROOTS-M@rootsweb.com>; Mon, 31 Jul 2006 17:22:03 -0600
Received: from JYoung6180@aol.com
	by imo-m20.mx.aol.com (mail_out_v38_r7.6.) id b.594.5d78af80 (29672);
	Mon, 31 Jul 2006 19:21:48 -0400 (EDT)
From: JYoung6180@aol.com
Message-ID: <594.5d78af80.31ffea8b@aol.com>
Date: Mon, 31 Jul 2006 19:21:47 EDT
Subject: Re: [ROOTS-L] Re: more on ancestry : incorrect ssdi listing
To: joanparker@intergate.com, ROOTS-M@rootsweb.com
MIME-Version: 1.0
Content-Type: text/plain; charset="US-ASCII"
X-Mailer: 9.0 SE for Windows sub 5031
X-Spam-Flag: NO
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

 
In a message dated 7/31/2006 4:18:01 PM Eastern Standard Time,  
joanparker@intergate.com writes:

Joan,

Glad you asked.

My error, close but no cigar, it  wasn't the SSDI, although that is what I
wrote, sorry.  It was the WWI  and WWII draft registrations, the 1920 and the
1930 census and the NYC  births.   It may not have been SSDI, but it
certainly shows five  Ancestry errors. Why put in a Year Range if it is going
to be ignored and  provide records way beyond the date?

However, despite the errors I am  still a devoted fan of  Ancestry.com!

Joanie




----
Joanie-
 
I see the problem...while you are specifying that you want exact matches  
only that isn't what you are getting in return.  This is a known bug -- see  the 
Ancestry Site Comments Board post by staff explaining that the bug in exact  
matches is being worked on:
 
 
<<http://boards.ancestry.com/mbexec?htx=message&r=rw&p=topics.ancestry.ancsite
&m=1689>>
 
This post will also answer many of the questions people have been raising  
since the changes appeared on the Ancestry pages.
 
Joan


