From roots-in@roots-l.rootsweb.com Sat Jul 29 09:58:33 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 k6TFwXjb012408;
	Sat, 29 Jul 2006 09:58:33 -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 k6TFwVMF009581
	for <roots-approved@rootsweb.com>; Sat, 29 Jul 2006 09:58:31 -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 k6TDJqFI007271
	for <roots-approved@rootsweb.com>; Sat, 29 Jul 2006 09:19:52 -0400
Received: (from roots-in@localhost)
	by roots-l.rootsweb.com (8.12.10/8.12.8/Submit) id k6TDJqdg007270
	for roots-approved@rootsweb.com; Sat, 29 Jul 2006 09:19:52 -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 k6TDG5FI007194
	for <roots-in@roots-l.rootsweb.com>; Sat, 29 Jul 2006 09:16:05 -0400
Received: (from slist@localhost)
	by lists5.rootsweb.com (8.12.8/8.12.8) id k6TFsWVB011085
	for roots-in@roots-l.rootsweb.com; Sat, 29 Jul 2006 09:54:32 -0600
X-Envelope-From: Kith-n-Kin@cox.net Sat Jul 29 09:54:32 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 k6TFsWjb011076
	for <ROOTS-M@lists5.rootsweb.com>; Sat, 29 Jul 2006 09:54:32 -0600
Received: from fed1rmmtao05.cox.net (fed1rmmtao05.cox.net [68.230.241.34])
	by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k6TFsSou007508
	for <ROOTS-M@rootsweb.com>; Sat, 29 Jul 2006 09:54:29 -0600
Received: from TOWER ([68.0.155.47]) by fed1rmmtao05.cox.net
          (InterMail vM.6.01.06.01 201-2131-130-101-20060113) with ESMTP
          id <20060729155423.RSQD12909.fed1rmmtao05.cox.net@TOWER>
          for <ROOTS-M@rootsweb.com>; Sat, 29 Jul 2006 11:54:23 -0400
From: "Kith-n-Kin" <Kith-n-Kin@cox.net>
To: <ROOTS-M@rootsweb.com>
Subject: RE: [ROOTS-L] Ancestry.com Question
Date: Sat, 29 Jul 2006 08:54:12 -0700
Message-ID: <009d01c6b327$3d7ebb90$6601a8c0@TOWER>
MIME-Version: 1.0
Content-Type: text/plain;
	charset="US-ASCII"
X-Priority: 3 (Normal)
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook, Build 10.0.6626
In-Reply-To: <bda.187b36f.31fbeb34@aol.com>
X-MIMEOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
Importance: Normal
X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34
X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34
Content-Transfer-Encoding: 8bit
X-MIME-Autoconverted: from quoted-printable to 8bit by admin.rootsweb.com id k6TFsWjb011076
Sender: roots-in@roots-l.rootsweb.com

I wonder if we are all seeing the same thing.

My first page (Home) has:
Tabs:
Historical Records; Family Trees; Stories and Publications; Photos and Maps
Under that is a check box for "Exact Matches Only"
Below that, with the search boxes, the one on the right has "Spelling: Exact or Soundex"
Below that is "Lived in (dropdown for country)" and then the dropdown for the (if US) state.
Then, Year range

Except for the tabs, this screen is almost identical to the "old" screen. 

I didn't see the old "Click on map" -- but finally found it. On the tabs across the top of the screen,
select "Search". The maps are at the bottom of the page.

As to the "soundex/exact" issue, it is still there, at least on my Home.

I'm not sure what the issue is on the number of people coming up on an initial search. As I recall, last
week, month, year. . .when I would put in "Henry Kleimnerschmidt", "Pennsylvania", "1800-1900", I would
get every "Henry Kleimnerschmidt" that showed up in any record with Pennsylvania (born, lived, died, etc)
that they had. I did find, then, the dating to be pretty loose. I would have to go the individual
database, and tweak the search. What people are describing now, sounds the same.

As to Ancestry World Tree (AWT) it doesn't seem to have a link to the "Home" page, but if you click on the
tab at the top that says "Family Trees" you will see a link on the right column under "Family Tree
Resources" that says "Search Ancestry World Tree."

I suggest that we all "play" with the site for a few days, then, if someone really can't find something
s/he misses, ask us, or ask Ancestry, for the information.

Pat (in Tucson)



