Thanks everyone. I went through thr marriage list one by one. It was easy to spot that way and unlinking was one of the options so I didn't have to go to family view to unlink each one. Going to the search multiple marriages didn't help me double check to see if I missed any but I may get ltools to do it. Dennis emailed me and said the deluxe version has that option.
Just FYI. I didn't pull in someone else's gedcom. I had a few of my own files that I had made mistakes on. Well basically I opened the wrong file and started working and I was worried I was going to miss something important. It was recommended that I do the intellimerge on as many files as I needed to. That worked great but for some reason I got all these duplicate marriages. Just one duplicate not one for each file merged. So I don't know what happened. I just needed to find the best way to fix it. I may have started to import one and stopped. Who knows? I don't think so but oh well. These things happen. It could have been worse. The marriage list option to unlink worked well. Kathy On Sunday, April 6, 2014, Cathy Pinner <[email protected]> wrote: > The merge shouldn't produce duplicate marriages. > > If it is, something is going wrong either in the > merge itself or the way it is being done. > > Of course David, the merge enables you to merge > people who don't have EXACTLY the same > information. Only the automatic bits of merge require EXACT. > > I don't think there are any new tools in the > merge part of Legacy in Legacy 8 apart from a > special merge using FamilySearch IDs. > > The merge isn't trouble free when it comes to > sources of events apart from the vital events. > I'm not sure of other problems but haven't tested merging for awhile. > > I have other reasons for not merging data from > someone else into my family file as a general > rule. Someone else rarely has the same standards > for data entry and sourcing that you have. I > think it's better to be slow but sure when entering data. > > However, we all have different reasons for doing family history. > > Cathy > > At 12:12 AM 7/04/2014, you wrote: > >Kathy, > > > >Did you happen to stop the merge process, then > >start it again? That can cause some problems. > > > >Also, there could be a glitch in the Legacy > >software, so you need to report it to Support. I > >had some sources duplicated by Legacy inserting > >normally hidden formatting code into text in > >notes and other places. It appeared to happen > >with only one revision of Legacy 7.5. A soon as > >the source notes are opened, the rogue > >formatting code disappears, so it is only > >visible in the preview. It was a lot of work to > >open all the duplicate sources, which removed > >the visible formatting code, and then use the > >new option to merge duplicate sources. > > > >Jay Ingalls > >================== > >On 4/6/2014 10:10 AM, David Abernathy wrote: > >>This is why most people will NOT merge data into their data files. > >>Ã' > >>If one is to look at Page 234 of the book and > >>then step 4 at the bottom of the page. It > >>states â EURO oemerges t those that have EXACTLY the same information.â > >>EURO  > >>Ã' > >>Since there was something different in these > >>marriages information a duplicated was made. > >>Ã' > >>Arenâ EURO (tm)t t these lovey new tools just GREAT. > >>Ã' > >>Ã' > >>Thanks, > >>David C Abernathy > >>Email disclaimers > > >>---------------------------------------------------------------------------- > >>This message represents the official view of the voices in my head. > > >>---------------------------------------------------------------------------- > >><http://www.SchmeckAbernathy.com>http://www.SchmeckAbernathy.com > >>== All outgoing and incoming mail is scanned by F-Prot AntivirusÃ' == > >>Ã' > >>From: Kathy Meyer [<mailto:[email protected] <javascript:;>>mailto: > [email protected] <javascript:;>] > >>Sent: Saturday, April 05, 2014 7:20 PM > >>To: <mailto:[email protected] <javascript:;> > >[email protected] > >>Subject: [LegacyUG] duplicate marriages > >>Ã' > >>I posted this before and didn't get any responses, so I'll try again :-) > >>Ã' > >>Somehow during a merge (Intellimerge) I ended > >>up with every single marriage related to the > >>merged file duplicated. Ã' Male #1 is married > >>to Female #2 twice; the 2nd marriage is > >>separate and does not link to the children of > >>the 1st marriage, which I am grateful for. Ã' > >>So as I've tried to figure this out on my own, > >>I have found the quickest way to remove these > >>marriages is to go to the marriage list and go > >>down the list one by one, visually noting the > >>duplicates, highlighting the bogus marriage (it > >>has a much higher RIN) and then making the 3 or > >>4 clicks to unlink each marriage. Ã' This has > >>been very time consuming but at least it's > >>better than trying to browse through the file > >>or having to be in family view to remove each link. > >>Ã' > >>I would like to be able to see a list of these > >>duplicate marriages that may still exist so I > >>can see where I am on it and what needs to be > >>done and ones I've overlooked. Ã' > >>Is there a way to create such a list? Ã' I > >>browsed through the search criteria for > >>marriages but it didn't seem to fit. Ã' I > >>haven't done a lot of searches though and definitely nothing this > specific. > >>Ã' > >>Thanks to anyone who can help! Ã' If it can't > >>be done, I hope a legacy moderator will at > >>least just tell me that I simply have to > >>continue going one by one through the marriage list. At least then I'd > know :-) > >>Ã' > >>Kathy Meyer > >>Ã' > >> > >> > >>Legacy User Group guidelines: > >><http://www.LegacyFamilyTree.com/Etiquette.asp> > http://www.LegacyFamilyTree.com/Etiquette.asp > >>Archived messages after Nov. 21 2009: > >><http://www.mail-archive.com/[email protected]/> > http://www.mail-archive.com/[email protected]/ > >>Archived messages from old mail server - before Nov. 21 2009: > >><http://www.mail-archive.com/[email protected]/> > http://www.mail-archive.com/[email protected]/ > >>Online technical support: > >><http://www.LegacyFamilyTree.com/Help.asp> > http://www.LegacyFamilyTree.com/Help.asp > >>Follow Legacy on Facebook > >>(<http://www.facebook.com/LegacyFamilyTree> > http://www.facebook.com/LegacyFamilyTree) > >>and on our blog > >>(<http://news.LegacyFamilyTree.com>http://news.LegacyFamilyTree.com). > >>To unsubscribe: > >><http://www.LegacyFamilyTree.com/LegacyLists.asp> > http://www.LegacyFamilyTree.com/LegacyLists.asp > >> > >> > >>Legacy User Group guidelines: > >><http://www.LegacyFamilyTree.com/Etiquette.asp> > http://www.LegacyFamilyTree.com/Etiquette.asp > >>Archived messages after Nov. 21 2009: > >><http://www.mail-archive.com/[email protected]/> > http://www.mail-archive.com/[email protected]/ > >>Archived messages from old mail server - before Nov. 21 2009: > >><http://www.mail-archive.com/[email protected]/> > http://www.mail-archive.com/[email protected]/ > >>Online technical support: > >><http://www.LegacyFamilyTree.com/Help.asp> > http://www.LegacyFamilyTree.com/Help.asp > >>Follow Legacy on Facebook > >>(<http://www.facebook.com/LegacyFamilyTree> > http://www.facebook.com/LegacyFamilyTree) > >>and on our blog > >>(<http://news.LegacyFamilyTree.com>http://news.LegacyFamilyTree.com). > >>To unsubscribe: > >><http://www.LegacyFamilyTree.com/LegacyLists.asp> > 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 > > > 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
