Jim To shorten and minimize the number of entries you would need to examine and verify for a merge, you could take the ‘OLD’ file and do a search for <individuals><date modified><after> <specified date> to create a list of entries changed AFTER the date of your initial mess up. You could then tag these entries and export exclusively to a temporary gedcom file which you could then import into your ‘NEW’ file for a minimum number of individuals to verify the needed corrections to. I am not sure, but I would believe this would include events, and location changes, etc. Maybe Sherry or Brian could verify this for you.
Good Luck either which way. Had a problem similar myself. Lots of work. Byron Schafbuch <http://freepages.family.rootsweb.ancestry.com/~byronsch/> The SCHAFBUCH family heritage site From: DimJim [mailto:[email protected]] Sent: Monday, January 07, 2013 12:51 PM To: [email protected] Subject: [LegacyUG] messed up my FDB file Hi group, Several months ago I messed up my family file when changing a *State* location field to a *City, County, State* location. Somehow, I managed to change EVERYONE with that *State* only location to the *City, County, State*. This goof involved nearly 600 persons and multiple Event locations. Not to worry..., rather than try to correct all of the errors, I just restored a recent backup into a NEW family file with a slightly different name. Then, another mistake -- I left the old, messed up file, in my Legacy folder, rather than deleting it. Then I went merrily on my way entering new people, additional events, sources, etc. Problem is, sometimes I would be using the NEW file and sometimes using the OLD messed up file. So now I have two family files with different record changes, deletions and additions made over the past several months. The OLD file with the corrupted locations, has 161 changes that the NEW file does not have. The NEW file has 312 changes that the OLD file does not have. I’m thinking that the easiest and most accurate way to bring the changes from the OLD file into the NEW file is to just Import the OLD file into the NEW file, then do a Merge. There are nearly 17,000 individuals in each file (48mg), but “probably” about 16,500 should merge automatically. ----- OR ------ Maybe I should make a list of those changes made in the OLD file, then do a Manual Merge on ONLY those items? Anybody have any thoughts on how best to solve my problem?..... traps or problems that I should look out for? Just thought I’d check for suggestions before I make matters worse. Thanks, Jim 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 No virus found in this message. Checked by AVG - www.avg.com Version: 2013.0.2805 / Virus Database: 2637/5991 - Release Date: 12/27/12 Internal Virus Database is out of date. 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
