Thanks for your previous comment about tagging everyone and then removing the tag, when each person is verified, when checking for duplicates. I decided to go through the entire name index and that is similar to what you suggested, but I won't have to tag anyone, except problems I want to research. Regarding the organization of the files, you said below:
You do not need to worry about continually updating multiple duplicate identical persons. Could you explain what you mean? I have to rely on other gedcoms from other family members and clean them up because in some cases, I would never get the information without that. But I want to find as workable a way as possible in combining the duplicates, so I was just wondering what you meant. Thanks, --Jerry Boor / http://www.MerriamFamilyTree.org/ On 8/2/2011 12:52 PM, RICHARD SCHULTHIES wrote: > Unless you have over 10,000,000,000 people in your DB, there is no > good reason to split the DB into separate files. And even then, it is > cleaner anyway. You do not need to worry about continually updating > multiple duplicate identical persons. I have 10 different > families/files mixed together in my DB. I have input whole books of > towns, too old for copyrights . In the days when hard drive prices > were cost prohibitave, you might NEED to do it. The computer doesn't > care if the people in the DB are related to each other. They don't > jump into wrong family printouts because of the size. > Rich jn LACA > -- On *Tue, 8/2/11, d /iamdad25@gmail. <mailto:iamdad25@gmail.>/* wrote: > > > From: d <[email protected]> > Subject: [LegacyUG] Legacy file organization > To: [email protected] > Date: Tuesday, August 2, 2011, 8:05 AM > > I need advice on how to organize my Legacy files. > > I am thinking, for example, that I should have one file with my > wife's lines and another with my lines. But then, what do I do > when I want to show the pedigree for my children? I also think > that I might want different files for active research data (which > can be messy and have unverified info, etc.) versus final/complete > data. And maybe different files to handle gedcoms, merging, etc. > Then I need strategies for how to manage all those files, when and > how to share data between them, how to share with others, when to > interact with newFamilySearch (and when not to!), etc., etc. > > Can you point me to any good discussions about these topics that > will help me to decide on my approach? > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Online technical support: http://www.LegacyFamilyTree.com/Help.asp > Follow Legacy on Facebook > (http://www.facebook.com/LegacyFamilyTree) and on our blog > (http://news.LegacyFamilyTree.com). > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Online technical support: http://www.LegacyFamilyTree.com/Help.asp > Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) > and on our blog (http://news.LegacyFamilyTree.com). > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
