From roots-in@roots-l.rootsweb.com Mon May 29 03:41:12 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 k4T9fCjb013024; Mon, 29 May 2006 03:41:12 -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 k4T9ejCH016179 for ; Mon, 29 May 2006 03:40:45 -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 k4T75iFI018558 for ; Mon, 29 May 2006 03:05:44 -0400 Received: (from roots-in@localhost) by roots-l.rootsweb.com (8.12.10/8.12.8/Submit) id k4T75ioG018557 for roots-approved@rootsweb.com; Mon, 29 May 2006 03:05:44 -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 k4SK6uFI017436 for ; Sun, 28 May 2006 16:06:56 -0400 Received: (from slist@localhost) by lists5.rootsweb.com (8.12.8/8.12.8) id k4SMfiTb018521 for roots-in@roots-l.rootsweb.com; Sun, 28 May 2006 16:41:44 -0600 X-Envelope-From: mscheffl@twcny.rr.com Sun May 28 16:41:44 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 k4SMfijb018510 for ; Sun, 28 May 2006 16:41:44 -0600 Received: from ms-smtp-03.nyroc.rr.com (ms-smtp-03.nyroc.rr.com [24.24.2.57]) by mail.rootsweb.com (8.13.4/8.13.4) with ESMTP id k4SMfhSR019842 for ; Sun, 28 May 2006 16:41:44 -0600 Received: from m1070n (cpe-24-92-248-107.twcny.res.rr.com [24.92.248.107]) by ms-smtp-03.nyroc.rr.com (8.13.6/8.13.6) with SMTP id k4SM73b4025547 for ; Sun, 28 May 2006 18:07:05 -0400 (EDT) Message-ID: <047601c682a3$0cc7d220$6801a8c0@m1070n> From: "MScheffler" To: References: <200605280943.k4S9h4fS028832@lists5.rootsweb.com> <004c01c68268$521734a0$49898445@marylynn> Date: Sun, 28 May 2006 18:07:02 -0400 MIME-Version: 1.0 Content-Type: text/plain; format=flowed; charset="Windows-1252"; reply-type=response 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-Virus-Scanned: Symantec AntiVirus Scan Engine X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34 X-Scanned-By: MIMEDefang 2.52 on 192.168.65.34 Subject: [ROOTS-L] Spliting database lines Sender: roots-in@roots-l.rootsweb.com Some of you may have very good reasons for splitting your maternal and paternal lines into separate databases. I personally would NOT do this however and advise anyone to think this through carefully if you are considering splitting your database. It may be difficult to go back should you want to. Most of the modern genealogy programs can hold up to millions of names so there is no problem with space keeping everyone in one database. As you add new generations to your starting point (assuming it is yourself) -- children, grandchildren, etc. they will need your maternal and paternal lines together to get their complete tree. If you give someone two separate trees, there will likely be lots of problems with merging. Unlinked or unrelated families in the database present no problems because only linked people get chosen for books/narrative reports that one is producing. I would guess that most if us, if we research long enough will find common ancestors in our maternal and paternal lines. I found this in several instances, and would not have guessed that as I was beginning. Having separate database for different parts of one's family will also require duplicate data entry if you are to keep all up to date. Personally data entry is something I do not want to have to duplicate. One good reason for splitting may be to send someone a gedcom file of only part of your material. That can best be done for that individual person and still keep using your own larger database. Personally I share my large database at WorldConnect and never send anyone other than close family complete gedcoms. I send ancestor and descendant reports when people want something not on WorldConnect, though most everything except my living people are there. All of my points are based on the fact that everything in my database is my own research is my own and I do not include gedcoms from other people in my master database except very occasionally and then only a few names from a good researcher whose data I have checked for accuracy and consistency before the import. If one uses gedcom files acquired from others, do put the "guest gedcoms" in their own databases, separate from one's own research. Merging material of unknown quality can cause corrupted databases, incorrect family links, duplicate names, various forms of places and sources, etc. Most of us make enough mistakes ourselves without taking on material of unknown quality. Gedcom is a wonderful feature for sharing data, but it needs to be used carefully. Margaret Scheffler ----- Original Message ----- > The more you get into genealogy, the more you realize you HAVE to split > your lines. I split my mother's line and my Dad's, then eventually her > parents and his etc. I have about 10 lines now. Probably more. > Marilynn > IBSSG