Before u start making changes dump a gedcom of everything and multipe backups, so you have a way to get back to your current state.
Depending on how new RIDs are assigned you might get a clue as to what was added last, so you can unlink last created and not screw up old links. SInce we are dealing with a database, it would sure be nice if a changelog was created showing adds, deletes and changes historically made. Maybe this will be a feature of REV 9? On Thu, Oct 15, 2015 at 1:29 PM, Diane Murach <[email protected]> wrote: > I have only used Legacy and have for many years. I’m thinking the > problem might have been in updates and perhaps it wasn’t finished but I try > to be careful about this or File/File Maintence/Check Repair > > > > Right now I have compared the original file (had the 380 error when making > descendant reports) to several new files that were created which have > scrambled marriages. Wondering about the MRIN numbers. > > > > The Original file error log reported: > > 67 ind records that reference a preferred marriage that does not exist. > The ones I’ve looked at all seem to be single people. > > 3 ind with a blank preferred marriage MRIN and those seem to have been > corrected. > > The rest is inconsistencies with names which doesn’t seem to be the > problem. > > > > I need to leave for a while, but I’ll check the first file that was made > as a solution to Error 380. It actually solved the error problem for a > short time. > > > > I’ll be back, > > > > Diane Murach > > > > > > *From:* Michele/Support [mailto:[email protected]] > *Sent:* Thursday, October 15, 2015 9:45 AM > > *To:* [email protected] > *Subject:* RE: [LegacyUG] Big problem > > > > Diane, > > Interesting. Has your file ever been in another program? It is pretty > hard to get Legacy to put a female into the husband’s spot. > > > > Send me an email at [email protected] Attn: Michele. Make a > backup of your file and attach the backup to the email. When you make the > backup just back up the data portion, leave the other boxes unchecked. I > will fix the more serious errors for you and then tell you what to do from > there. > > > > Michele > > Technical Support > > Millennia Corporation > > [email protected] > > www.legacyfamilytree.com > > > > *From:* Diane Murach [mailto:[email protected]] > *Sent:* Thursday, October 15, 2015 12:37 PM > *To:* [email protected] > *Subject:* RE: [LegacyUG] Big problem > > > > > > I have only imported my own legacy gedcom into a new legacy file to fix > Error 380. I have never imported anyone else’s gedcom into my file as I > always analyze first. Everything in my file has been entered manually. > > > > Major problem as some of these people are Swedish and use the old naming > patterns and I have no idea who they belong with. Also many generations > of sibling descendants so I am unsure who belong with whom. > > > > Does it matter who I unlink from whom? I guess I am supposed to unlink > all these messed up marriages. I will wait for verification before doing > anything. > > > > Diane > > > > > > *From:* Michele/Support [mailto:[email protected] > <[email protected]>] > *Sent:* Thursday, October 15, 2015 9:19 AM > *To:* [email protected] > *Subject:* RE: [LegacyUG] Big problem > > > > Diane, > > These are the kinds of errors you see when you import a gedcom or directly > download a chunk of tree from FamilySearch. You are inheriting other > people’s mistakes. > > > > I would print the Check/Repair error log and just go down the list one at > a time. These problems need to be fixed first. Once you can run a > Check/Repair with no errors you can work on the Potential Problems list of > possible problems. > > > > Michele > > Technical Support > > Millennia Corporation > > [email protected] > > www.legacyfamilytree.com > > > > *From:* Diane Murach [mailto:[email protected] <[email protected]>] > *Sent:* Thursday, October 15, 2015 12:13 PM > *To:* [email protected] > *Subject:* [LegacyUG] Big problem > > > > I believe I have a huge mess with a scrambled database and unsure how to > resolve this. > > I have a 8 page list errors with as an example a woman b 1941 married to a > man born in 1886 in Sweden and the marriage is 50 years before either were > born. > > > > Earlier I had an error 380 and could not print a descendant report. We > followed the directions to correct it, but still not corrected. Now the > problem has expanded. > > > > Results of Error Log > > 19 marriage records where husband is in the female position and not to the > correct wife. > > > > 17 marriage records where the wife is not female. > > > > 5 individuals never married but they are married > > > > 69 individuals that reference a preferred marriage record that has been > removed > > > > 13 male individuals with a different husband > > > > 12 females with a different wife. > > > > Resetting of MRIN numbers > > > > Direction please on how to repair and how to avaoid this happening again. > > > > Diane > > > > 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 > > > 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
