From roots-in@roots-l.rootsweb.com Sun Jul 23 11:45:54 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 k6NHjsjb024650;
	Sun, 23 Jul 2006 11:45:54 -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 k6NHjqhD016892
	for <roots-approved@rootsweb.com>; Sun, 23 Jul 2006 11:45:52 -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 k6NF7YFI010491
	for <roots-approved@rootsweb.com>; Sun, 23 Jul 2006 11:07:34 -0400
Received: (from roots-in@localhost)
	by roots-l.rootsweb.com (8.12.10/8.12.8/Submit) id k6NF7YXN010490
	for roots-approved@rootsweb.com; Sun, 23 Jul 2006 11:07:34 -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 k6NEuvFI009668
	for <roots-in@roots-l.rootsweb.com>; Sun, 23 Jul 2006 10:56:57 -0400
Received: (from slist@localhost)
	by lists5.rootsweb.com (8.12.8/8.12.8) id k6NHZ4R3018710
	for roots-in@roots-l.rootsweb.com; Sun, 23 Jul 2006 11:35:04 -0600
X-Envelope-From: sdepuy@mhcable.com Sun Jul 23 11:35:04 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 k6NHZ4jb018701
	for <ROOTS-L@lists5.rootsweb.com>; Sun, 23 Jul 2006 11:35:04 -0600
Received: from smtp-gw.mhcable.com (smtp-gw.mhcable.com [24.105.198.42])
	by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k6NHZ1T7009085
	for <ROOTS-L@rootsweb.com>; Sun, 23 Jul 2006 11:35:01 -0600
Received: from localhost (localhost [127.0.0.1])
	by deliver.mhcable.com (Postfix) with ESMTP id F145CE722A
	for <ROOTS-L@rootsweb.com>; Sun, 23 Jul 2006 13:35:01 -0400 (EDT)
Received: from smtp-gw.mhcable.com (localhost [127.0.0.1])
	by localhost (VaMailArmor-2.0.1.16) id 25784-1A24AC3C;
	Sun, 23 Jul 2006 13:35:01 -0400
Received: from sd (24-105-206-167.cm.mhcable.com [24.105.206.167])
	by outgoing2.mhcable.com (Postfix) with SMTP id D16B8E722A
	for <ROOTS-L@rootsweb.com>; Sun, 23 Jul 2006 13:35:01 -0400 (EDT)
Message-ID: <002f01c6ae7e$54128510$6a01a8c0@sd>
From: "Sharon" <sdepuy@mhcable.com>
To: <ROOTS-L@rootsweb.com>
References: <200607231631.k6NGVbuv012265@lists5.rootsweb.com>
Date: Sun, 23 Jul 2006 13:35:01 -0400
MIME-Version: 1.0
Content-Type: text/plain;
	format=flowed;
	charset="iso-8859-1";
	reply-type=original
Content-Transfer-Encoding: 7bit
X-Priority: 3
X-MSMail-Priority: Normal
X-Mailer: Microsoft Outlook Express 6.00.2900.2869
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2869
X-AntiVirus: checked by Vexira MailArmor (version: 2.0.1.16; VAE: 6.28.0.18; VDF: 6.28.0.106; host: smtp.mhcable.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
Subject: [ROOTS-L] CAn SOMEONE PLEASE EXPLAIN - Death records

I'm not sure about CA's policy, but here in NYS there is a privacy policy in 
effect which has been in place for many years -- for genealogical research a 
death must have occurred at least 75 years before the search date. Birth and 
marriage dates must have been at least 50 years before the search date and 
the parties involved (i.e. the person born or the bride and groom) must be 
deceased. Of course, if you are the person involved and need a birth or 
marriage certificate, that is a different story, or a next of kin or estate 
attorney can obtain a death certificate for a more recent happening. Even 
then, NYS does not make these records available on line. Sharon in NY
> X-Message: #6
> Date: Sat, 22 Jul 2006 22:40:09 -0600
> From: Yourprayingaunt@wmconnect.com
> Subject: CAn SOMEONE PLEASE EXPLAIN
>
> Being all new to genealogy search I noticed that when I do Rootsweb/Calif.
> Death Records for family members that I know death dates on and all the
> information on most and it will come up no match. This is true on the LDS 
> site and I
> am having to stay with the free ones and get no place. Do we know why you 
> just
> cannot go to a state and get this info sense its public record? Or maybe I 
> am
> wrong on this being public record.  Thank you for any help.
>
> ------------------------------
>


