From roots-in@roots-l.rootsweb.com Thu Jul 27 18:38:51 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 k6S0cpjb009843; Thu, 27 Jul 2006 18:38:51 -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 k6S0co2L012437 for ; Thu, 27 Jul 2006 18:38:50 -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 k6RM0HFI001434 for ; Thu, 27 Jul 2006 18:00:17 -0400 Received: (from roots-in@localhost) by roots-l.rootsweb.com (8.12.10/8.12.8/Submit) id k6RM0HXw001433 for roots-approved@rootsweb.com; Thu, 27 Jul 2006 18:00:17 -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 k6RLqIFI001363 for ; Thu, 27 Jul 2006 17:52:18 -0400 Received: (from slist@localhost) by lists5.rootsweb.com (8.12.8/8.12.8) id k6S0UeKY007336 for roots-in@roots-l.rootsweb.com; Thu, 27 Jul 2006 18:30:40 -0600 X-Envelope-From: marilyneb@gmail.com Thu Jul 27 18:30: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 k6S0Uejb007325 for ; Thu, 27 Jul 2006 18:30:40 -0600 Received: from ug-out-1314.google.com (ug-out-1314.google.com [66.249.92.170]) by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k6S0UaCx006781 for ; Thu, 27 Jul 2006 18:30:37 -0600 Received: by ug-out-1314.google.com with SMTP id k40so569736ugc for ; Thu, 27 Jul 2006 17:30:37 -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=Sda+ZygH2Zb2rbi0J2wds32mvdcDLnGR4FCD4rV5f27vUhdZv9aNYbWogvhx+yyyrfs2TquJYyQ5RpecYGFDBahx+buu/mZZd9fP10p4MF09j9JO+hz8cpyeNGmtTohpP+SedhGa1Bt9LVcBscnqG67sPLIbmus1Gk0+oRWMlgc= Received: by 10.67.93.7 with SMTP id v7mr7923218ugl; Thu, 27 Jul 2006 17:30:37 -0700 (PDT) Received: by 10.67.22.6 with HTTP; Thu, 27 Jul 2006 17:30:36 -0700 (PDT) Message-ID: <65d66f240607271730o75d30ec4m9bbff5297150e20d@mail.gmail.com> Date: Thu, 27 Jul 2006 19:30:36 -0500 From: "marilyn e brown" To: "huggins huggins" Subject: Re: [ROOTS-L] Ancestry.com Question Cc: ROOTS-M@rootsweb.com In-Reply-To: <20060727225754.95671.qmail@web51805.mail.yahoo.com> MIME-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-1; format=flowed References: <20060727225754.95671.qmail@web51805.mail.yahoo.com> 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 You weren't wrong. I just tried to save a record to Ancestry. All those Census Records, Draft Cards, and etc. No way to access them. I did send them an email through "help". It was not a happy email. What it seems they are wanting is for us to start putting our information online. I feel as if I am being coerced into something I am not ready to do. I wonder when this all took place? I noticed yesterday the home page had changed when I was doing a couple of searches for someone from another list. Now I am going back to see what other changes they have made. I am not a happy camper. Marilyne On 7/27/06, huggins huggins wrote: > > I can no longer save census records to "My Ancestry". > There are 2 choices - save to "Shoebox" or "Start a > New Tree With This Name" (or wording similar). > > The actual census page can be saved to "Shoebox", > "Start a New Tree" or "My Computer". No "My > Ancestry". > > I loved the "My Ancestry" layout and am not sure why > it was deleted as a choice. > > I clicked on "Contact Us" at Ancestry.com and wrote up > the question. When I hit the "Submit" key, it opened > to a page that said, "The page cannot be displayed - > HTTP Error 405". (Figures!) > > Then I went to the message boards to post the question > but couldn't find a link to post a new message. > Instead, there's an error that states, "You are not an > administrator". I made sure I was logged in but still > had the same problem. > > Is anyone else facing the same issues??? > > Thanks, > dee > >