I agree with you completely. I was only suggesting how Millennia might fix it so when a duplicate is detected during data entry it might combine it and then jump to merging siblings, spouses, parents, and children of those combined like it does when doing a manual merge. That should resolve the duplicate marriages, etc. that you described. Ron Taylor
On Saturday, March 1, 2014 2:57 PM, Bob Austen <[email protected]> wrote: Thanks Ron. However I’m not sure that you actually tested it, or are of the belief that it should work (of course it should). I tried it again after a file maintenance, and even on the sample data and get the same results. This seems to work fine if you are adding new data with the “Check for duplicates” enabled, as it will check on the first person entered. If you say that it is not a match then it won’t make the match when you enter a duplicate spouse. This is as it should be – the first name will now be tagged “not a duplicate” I have many names in my file prior to this “check for duplicates while adding new individuals”. Let’s say I have Asa Clark Brown entered twice in my file, and I discover his wife is Eleanor Huffman. As soon as I add Eleanor the program checks for a duplicate, to which I say “yes” it is. It will merge the two Eleanor Huffman’s and keep the two husbands – both with identical information (duplicates) I am now convinced it is an “oversight” (thanks Geoff) on the part of Legacy and will forward this to them as well. Many thanks, Bob A From:Ron Taylor [mailto:[email protected]] Sent: Saturday, March 01, 2014 1:13 PM To: [email protected] Subject: Re: [LegacyUG] Match on new entry I can't confirm your observation but the program probably should be treating these new match/merges the same as the manual merge so that after completing the merge of the two people considered duplicates then it should jump to merging all those related to that combination. The logic is already invoked after a manual merge. Ron Taylor On Friday, February 28, 2014 8:24 PM, Bob Austen <[email protected]> wrote: After entering a new name Legacy may find a match in my file. If I click on “Yes, this is a match” then it very nicely takes me to the merge screen and I can agree to the merge. My issue – if this merge is one spouse of a married couple, it just merges this person but not the other spouse. I now have this person with 2 spouses (the same) and I then have to do another merge for these 2 other spouses. I find this odd and annoying, especially when the regular merge will offer to merge the other spouse as well. Are others experiencing the same? Perhaps I just need to run maintenance. Bob A 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
