Yes that's right. You only use Gedcoms to transfer to an earlier version of Legacy or another program or website, like Ancestry.
Cathy At 06:18 PM 28/04/2014, you wrote: >Dear Cathy > >Thank you for your response and its clarity. > >I assume he would import as a Legacy file and not a gedcom? > >With thanks > >Anne > > > >-----Original Message----- >From: Cathy Pinner >Sent: Monday, April 28, 2014 6:56 PM >To: [email protected] >Subject: Re: [LegacyUG] Two files > >Hi Anne, > >Let me see if I understand what he is wanting to do. > >He has 3 files. > >1) His original file > >2) The file of his new contact > >3) The new file he created to make sense of the new data. > >He is now wanting to combine 1 & 3 as 1 has other lines as well? > >So the answer is to import 3 into 1 and then do a >merge of the people who are the same. > >Depending on the new file, it may be easier to >delete the branch from the original file (File 1) >and import File 3 to take the place of that >branch. Once imported the links can be made >between the people in the two files and any >remaining duplicates merged. If there are a lot >of duplicate people and he wants to replace the >originals with the ones from File 3 then that >would be the simplest way. However if he wants >some information from the person in File 1 and >some from the same person in File 3 then you have >to use the merge dialogue and choose which bits of each you want. > >The main thing is to do a backup of each file >before you start - and make sure you can restore >them (remember to give the file a new name so it >doesn't overwrite the original file). Then it >doesn't matter what happens with the importing >and merging as you can start again. There's >nothing like doing a merge to learn how best to do it. > >One trick is to make sure to use the option on >importing a file to start the RINs at a much >higher number than the RINs in the original file. >Then during the merge you can easily tell who >comes from which file. It also helps you decide >whether the pair presented are the same person >and need to be merged. If they come from the same >file, they probably are not duplicates and can be skipped. > >Once you've finished the import and merge you can >use the Tools Renumber RINs to get rid of gaps in the RINs. > >I'm not sure what your concern is re the merge. >You can choose which information you keep and >with the main name you can choose to make the >variant an AKA and with vital event dates that >are different you can choose to keep both by >choosing to make one an Alt. Event eg Alt. >Birth. A little square is next to the field name >for names, dates and locations. Clicking on it >gives you options of what to do with the data >that hasn't been chosen with the radio button. > >The merge shouldn't lose data. There is a problem >I think with merging identical individual special >events in that the sources are not necessary >merged. In the situation you are describing, that >probably is not going to be an issue. > >As I said, the best way to find out what can be >done is to do it. If you have proper backups, you >can always abandon what you've done and start again. > >Cathy > >At 02:58 PM 28/04/2014, you wrote: > >Hello > > > >I am attempting to assist a friend who has > >Legacy. I am not at all conversant with Merging, > >single instances only, or importing a file either gedcom or legacy > >database. > > > >Recently he was contacted by someone who is of > >the same tree as him with European roots. > > > >On looking at his tree and theirs and the large > >numbers of surname variants, some of which he > >had no record of and he therefore decided to start a new database. > > > >There were several cases of same surnames > >marrying with a few years of each other and > >varying other issues dates etc. which again led > >him to believe he needed to begin > >again with a separate tree to assist him to sort them all out. > > > >Having now finished this (and finding out he had > >connected his own line to one of the many same > >name marriages) he now has a correct tree in > the ââ¬à ânewââ¬ìàfile. > > > >His problem is how does he get the new file into his own tree. > > > >I have read the Merge files section of help and > >feel this may not solve the problem as I am not > >sure that this will cope with the differences, particularly with the names. > > > >I hope my explanation is clear enough and would > >appreciate any advice regarding this problem. > > > > > >Anne Wiltshire > >QLD Australia > > > > >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
