Robert, I'm thinking you will have to use the Merge program. I would think that Legacy imports what it gets without using any "cleaning" step, probably since that "cleaning" step is available with the merge programming.
Sometimes two people are very similar in data entry, and you don't want Legacy to make the assumption that they are the same person. And also, sometimes genealogists do enter a person in their tree more than once, without knowing it, and so when they use the merge function, Legacy points out these connections, helping them to intelligently connect two lines they weren't previously aware of. I don't know all this for sure from a programming standpoint, but I have used GEDCOM imports, then merges, and that is when Legacy has pointed out the same people to me. I hope this helps, Susan On Sat, May 24, 2008 at 4:54 PM, Robert Carneal USA < [EMAIL PROTECTED]> wrote: > If I have a faulty Gedcom which appears to contain the *same* person more > than once (That is, birth, marriage, divorce, death, spouses, etc. are the > same), what is Legacy supposed to do? Import them anyway as two (or more) > SEPARATE people, and the user therefore has to go through the file and merge > (or delete) the repeated people? Or, have any of you managed to use Legacy > as a Gedcom 'cleaner' of sorts? > > Doesn't matter -how- it happened, I just want to efficiently clean it up. > <g> > > I doubt if the Gedcom author can be located, since no one in the group > knows it was. I suspect the author was probably working from photographs of > headstones, and whenever a headstone was photographed more than one, so then > that person got entered into a family file more than once, but I am not > sure. > > Thank you. > > Robert > Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
