Hey JLB - thanks for the thoughts on just exporting and merging those records changed AFTER my Goof Date. I may just give that a try. I suppose I must export not only those people with changes after Goof Date, but also their spouse, parents, and children to be sure that I get the Linkages done properly in the NEW file. thanks again, Jim
On Mon, Jan 7, 2013 at 12:26 PM, JLB <j...@jgen.ws> wrote: > Your plan sounds OK to me. If I was doing it I would probably merge both > the files to make sure I don't miss anyone. Otherwise, do a search for > Modified After (date) on one file, export and merge that into the other. > ----- > JL Beeken > JLog - simple computer technology for genealogists > http://jlog.jgen.ws/ > > On 1/7/2013 10:51 AM, DimJim wrote: > > 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/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://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/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://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/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://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
