From roots-in@roots-l.rootsweb.com Sat Jul 29 08:09:19 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 k6TE9Jjb014192;
	Sat, 29 Jul 2006 08:09:19 -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 k6TE9Fxr025431
	for <roots-approved@rootsweb.com>; Sat, 29 Jul 2006 08:09:15 -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 k6TBUbFI006881
	for <roots-approved@rootsweb.com>; Sat, 29 Jul 2006 07:30:37 -0400
Received: (from roots-in@localhost)
	by roots-l.rootsweb.com (8.12.10/8.12.8/Submit) id k6TBUbDv006880
	for roots-approved@rootsweb.com; Sat, 29 Jul 2006 07:30:37 -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 k6TARLFI006716
	for <roots-in@roots-l.rootsweb.com>; Sat, 29 Jul 2006 06:27:21 -0400
Received: (from slist@localhost)
	by lists5.rootsweb.com (8.12.8/8.12.8) id k6TD5oZn013235
	for roots-in@roots-l.rootsweb.com; Sat, 29 Jul 2006 07:05:50 -0600
X-Envelope-From: omchodoy@gmail.com Sat Jul 29 07:05:50 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 k6TD5ojb013224
	for <ROOTS-M@lists5.rootsweb.com>; Sat, 29 Jul 2006 07:05:50 -0600
Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.168])
	by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k6TD5jV1006157
	for <ROOTS-M@rootsweb.com>; Sat, 29 Jul 2006 07:05:46 -0600
Received: by ug-out-1314.google.com with SMTP id m2so125806uge
        for <ROOTS-M@rootsweb.com>; Sat, 29 Jul 2006 06:05:46 -0700 (PDT)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:cc:in-reply-to:mime-version:content-type:references;
        b=g2AKS643a8FfllNqfhbBs+sreFx1ri8OrSUNM7tZ8xDynarmV0Dk5UQx9eG2NpCsLo1XQbNtYzascYlUpdXlDBOSkJjY5iCHA+4XwnQ3sPTSFQ56BDA+GsY+CaASbts8eVpmibDvXwhKQ0KScgunte+VhITnLT2XQsdAajfVOpg=
Received: by 10.67.89.5 with SMTP id r5mr599227ugl;
        Sat, 29 Jul 2006 06:05:45 -0700 (PDT)
Received: by 10.66.220.16 with HTTP; Sat, 29 Jul 2006 06:05:45 -0700 (PDT)
Message-ID: <d9cf5f330607290605k11f9e8e7ube157011c8c05eb2@mail.gmail.com>
Date: Sat, 29 Jul 2006 06:05:45 -0700
From: Colleen <omchodoy@gmail.com>
To: "Mary Putman" <mputman@gohighspeed.com>
Subject: Re: [ROOTS-L] Information on Ancestry
Cc: ROOTS-M@rootsweb.com
In-Reply-To: <00e301c6b2d7$5c7f57c0$84812340@eozfaqvf>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
References: <00e301c6b2d7$5c7f57c0$84812340@eozfaqvf>
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

I get that  happening too, and from what I've seen so far, it's still
happening.  I'll type in the name DOYLE with United States and Pennsylvania
on the initial search and get a results page.  When I click on a result, I
get tons of results from all states; however all had PA as the birthplace,
so I'm assuming that's why they all came up.  HOWEVER,  when you click on a
result in the inital result page, you can then scroll down to the bottom of
the page and narrow the search to the area you're searching.  You'll have to
do this fore every result you click on.For example, the initial result page
will list 2,567 results in 1910 US Census.  I click on that, then scroll
down to narrow the search. If I go back to the initial result page and click
on 1920 I'll have to narrow it down again.

Seems it would be more efficient if they had two location fields: 1 for
birthplace and 1 for place you're searching.

Still, I love ancestry.com and think it is the best out there.  Most of the
time, it sure beats scrolling through every page of the census for a
specific town (though I've learned from doing that, too, but when I'm
looking for something specific, who has time to look at every page?).




On 7/28/06, Mary Putman <mputman@gohighspeed.com> wrote:
>
>
> While searching census at the computer a couple of days ago about
> 11:30pm,  I had a notice that Ancestry was shutting down for a few hours to
> upgrade some items.   I didn't particularly like it when they upgraded
> before.  Since that upgrade, If I type in a name, time period, and state,
> all that comes up is everyone by that name in every state!  I have to then
> scroll through about 10 pages of data before I find the person and state I
> need.  Frustrating and very time-consuming!  I'm still with Ancestry, but
> I'll see  what happens in the future.  When they upgraded last time, they
> surely did "fowl up" reading any of the newspaper items.    Mary P.
>
>


-- 
Colleen
www.omchodoy.blogspot.com
www.onlyingenealogy.blogspot.com

