Hi Brian, Sorry about this. I've seen this on a smaller scale but couldn't reproduce it.
Your easiest way (unless this group is larger) would be to search on Modified Date and tag and export all those modified after the date of a backup that's OK. Then merge or use Split screen and copy and paste change details. If it is a larger group, again use Split Screen with one side using a backup that's OK and the other the one where the location has changed so that you don't have to research what the correct location is. Keep an eye on whether it was one location that was changed to the wrong one or a mix. I think the bug is something to do with merging locations and a wrong merge happens. Cathy Kathy Meyer wrote: > > Soooo sorry to hear this. Wish I could give advice but I do empathize > with you. I had a bunch of marriages duplicated once and had to go > through every one individually. But at least the group was able to > help me do it The fastest way possible. > > On Wednesday, February 18, 2015, Brian L. Lightfoot > <[email protected] <mailto:[email protected]>> wrote: > > I was entering a new location today and jumped into the Master > Location List to edit the Short Name Location. But that’s when I > noticed that there were two identical location with the same name. > I clicked on the other one and was surprised to see a very large > list of names associated with that location….something that I knew > was impossible. Then Legacy opened up and ERROR window and > recommended that I do a File Repair. I did that with no other > warnings, and went back to my list to now discover that > approximately 5,000 names have their birth location associated > with the new location.____ > > __ __ > > I don’t know which is easier, go back to a recent back-up and lose > all my work from the past few days, or tag all these people with > the wrong location and edit each one individually.____ > > __ __ > > I think I just take 2 aspirins.____ > > __ __ > > __ __ > > Brian in CA____ > > __ __ > > > > 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://support.legacyfamilytree.com > 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://support.legacyfamilytree.com > 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://support.legacyfamilytree.com 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
