<<Someone also referenced Intelimerge, but I'm not sure what that is... Part of legacy?>>
It is a part of Legacy. It was designed so that one person could assemble updates from several others then send the updated file back out for more work by the group. Legacy assigns a code to each individual in the database, and when a merge is called for it compares each person. When there has been no change in an individual, it just goes on to the next one. Only changes are presented for your approval. You put in two files that were originated on your machine, and merge them. It will go through them, with your permission, and pass over those with no changes, then it presents the changed ones to you. So if you have two backups that are different, all you will see when you merge them is the changes you have made. Try it out with copies of your files to see how it works. Carl 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
