Also Kathy and Brian are what I consider "power users" (always helpful answering questions and know Legacy quite well) and have been using Legacy for awhile. My concern is that if this type of things happens to you two, what are the chances others (including me) might also have this happen (and perhaps not even notice it until many days or weeks have passed). Really want those popups or reminders that what we have done might have an affect we did not contemplate (big fan of warnings). Thanks
Tessa *Tessa Keough* *Guild of One-Name Studies, **Keough (Keogh, Kough & Kehoe) Registered ONS* *Legacy Virtual Users' Group Community on Google+* *Society for One-Place Studies - Plate Cove East, Newfoundland * On Thu, Feb 19, 2015 at 8:17 AM, Kathy Meyer <kmeyer2...@gmail.com> wrote: > Is there a way to open the in messed up file side by side to go through > only the individuals where changes had been made over those two days? Like > create a report on recently edited individuals? Or are you comfortable > remembering which ones you worked on? Is there a way to see only those > individuals if you wanted to? ThT would certainly help me from time to > time. :-) > > As for my duplicate marriages - it happened after a merge process. I > probably did something wrong but never tried to figure out what that was. > Just wanted to fix it. And I did get it done. It was just under 1000 > marriages. Now if it had been 5000 I may have made a different choice > > Kathy > > On Thursday, February 19, 2015, Brian L. Lightfoot < > br...@the-lightfoots.com> wrote: > >> This data destruction occurred on its own. I was merely editing a Short >> Location Name when I noticed the screen blinked and suddenly there were two >> such locations, one legit and one with the approx. 5,000 names. >> >> >> >> I’ve never had it happen before and I doubt if I could ever duplicate it. >> I now wonder if I had just exited Legacy without saving and restarted >> instead of doing a file check/repair which seemed to cement the erroneous >> locations to the persons. Blame it on the solar winds. >> >> >> >> While in the Master Location list, I could easily tag the list of 5,000 >> and as suggested could use a split screen with a recent backup but then I >> started to estimate the time needed to wade through such a list. I may not >> live that long. >> >> >> >> I opted to jump back 2 days and use the last back up as a starting point. >> Not really all that bad because all I did for 2 days was to add census >> images and they are still there in the media folder. >> >> >> >> By the way, in case you were wondering, this was v8. >> >> >> >> >> >> Brian in CA >> >> >> >> >> >> *From:* Tessa Keough [mailto:murke...@gmail.com] >> *Sent:* Wednesday, February 18, 2015 4:22 PM >> *To:* legacyusergroup@LegacyUsers.com >> *Subject:* Re: [LegacyUG] Oh-oh! >> >> >> >> Does this type of thing just happen on its own Kathy or Brian OR was >> there some type of user error. If it just happens, that doesn't provide a >> whole lot of confidence as to integrity of the data entered. It is a bit >> more concerning than oh-oh. Can anyone explain why it happened? >> >> >> >> Tessa >> >> >> *Tessa Keough* >> >> *Guild of One-Name Studies, **Keough (Keogh, Kough & Kehoe) Registered >> ONS* >> >> *Legacy Virtual Users' Group Community on Google+* >> >> *Society for One-Place Studies - Plate Cove East, Newfoundland * >> >> >> >> On Wed, Feb 18, 2015 at 2:08 PM, Kathy Meyer <kmeyer2...@gmail.com> >> 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 < >> br...@the-lightfoots.com> 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/legacyusergroup@legacyusers.com/ >> Archived messages from old mail server - before Nov. 21 2009: >> http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ >> 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/legacyusergroup@legacyusers.com/ >> Archived messages from old mail server - before Nov. 21 2009: >> http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ >> 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/legacyusergroup@legacyusers.com/ >> Archived messages from old mail server - before Nov. 21 2009: >> http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ >> 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/legacyusergroup@legacyusers.com/ >> Archived messages from old mail server - before Nov. 21 2009: >> http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ >> 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/legacyusergroup@legacyusers.com/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > 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/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ 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
