Laird - Thanks a million - that is the best explanation I have ever seen on this subject. The numbering at the highest point is a revelation to me and well worth trying. Many thanks for the clarity and the response.
Bob On Apr 8, 2012, at 10:34 PM, Laird wrote: > Robert, > In addition to importing your GEDCOM into a new file and clean it up first. > You > can add one or more sources to indicate where you got the GEDCOM from etc. > When > it is time to merge it with your main data base: > > Maintain the new file as a Legacy file, DO NOT export it as a GEDCOM to be > merged with your main database. > BACKUP....BACKUP, maybe rename. > > When you import the newfile.fdb, tell Legacy to renumber the individual [RIN] > and marriage [MRIN] numbers to a number exceeding the highest numbers in your > main database. Say if you had 10,000 individuals in your main database and > your > highest RIN was 11, 381 (you will likely have some skipped numbers and this is > OK, don't worry about it) , you might renumber the import starting with 11,382 > or a little higher. To find the highest RIN in your main database select the > index tab and click the RIN button at the top left of window. Then scroll to > the bottom of the list and note the highest RIN used. > > Same story with the MRINs. To find the highest MRIN go to View>Marriage List, > click MRIN in the top left of window and scroll to the bottom of the list and > note the highest number used. > > Next you will go to: File > Import From > Legacy File> and find your > newfile.fdb and click open. You will select Add the Legacy information to > the > EXISTING Family File. Click Proceed, Continue with import and a new window > named Legacy Import will open . This is where you renumber the RINs, in > the > upper right of the window, select Renumber RINs from: put a number higher > than your highest RIN as noted above. Also do MRINs from: with the higher > MRIN as noted above. > > When you are ready click the Start the Import button. When you do the > merge/check for duplicates you will know all the new import numbers are higher > than your main database. After the merge the duplicates will become unused > RIN/MRINs. Again don't worry about it. > Laird > > On 4/8/2012 10:55 AM, R G Strong-genes wrote: >> I agree. Are you importing the gedcom directly into your file? You should >> import it into a NEW file then do all your duplicate checking, place name >> formats etc, etc. BEFORE you merge it into your main database. This will >> eliminate most of your duplicates and will merge more smoothly plus you can >> create the source for that GEDCOM and the info will import with the new >> source. >> Russ >> *From:* RICHARD SCHULTHIES <mailto:[email protected]> >> *Sent:* Sunday, April 08, 2012 4:52 AM >> *To:* [email protected] >> <mailto:[email protected]> >> *Subject:* Re: [LegacyUG] Duplicate Problem >> You just have to buckle up and do the Merge/Unlink like we all do. No easy >> answer. Sorry, Rich in LA CA >> *From:* RUNION ROBERT <[email protected]> >> *To:* [email protected] >> *Sent:* Saturday, April 7, 2012 2:50 PM >> *Subject:* [LegacyUG] Duplicate Problem >> >> I received a GEDCOM file that I would like to add to my files (to a backup >> copy just as a safeguard). In importing the GEDCOM of approximately 2000+ >> names, I have discovered duplication of about half of the persons imported. >> Is there a recommended way to eliminate the duplications? I tried the >> duplication process and it appears that I have to address each pair >> separately. This creates a problem when looking at the names and data as to >> which one is the accurate one or even if it is a duplication. Suggestions? >> > > > > 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
