Brian, Brian at Legacy answered BUT: There are several disadvantages to exporting / reimporting via gedcom. Everyone shows as IMPORTED. It might appear that you borrowed your database from someone else. Modified dates all reset. To-do list loss? I'm sure there are other drawbacks.
-- Richard Van Wasshnova On Tue, Dec 15, 2009 at 3:10 PM, <[email protected]> wrote: > > File merging seems to have produced erroneous links with both Legacy 6 and > Legacy 7. Under Legacy 6, I found duplication of parents with children > linked to only one set. That was picked up by either noticing doubled > spouses on the Family Screen, or that the tree could be traversed one way but > not the other. It was fixable by appropriate delinking of the childless > parents. > > My last merge with Legacy 7 similarly produced a tree traversable down but > not up from files lacking that feature, stopping at a parentless individual, > but with no other information or apparent tool in Legacy to fix it. (No > duplication of child or parents.) Accordingly, I exported a gedcom to > GRAMPS, where the individual showed up with two parent sets, one correct and > the other two "Unknown". It's trivial in GRAMPS to delete the bad link, so I > did that and returned the genealogy to Legacy 7 via gedcom with the problem > found fixed. No change appeared in the individual count in GRAMPS or Legacy, > nor did it earlier in Legacy 6, and "File Repair" fails to fix this. > > My questions: Is there a way to search Legacy 7 for this kind of problem? > Is there a way to fix the parent duplication one in Legacy 7? > > kb > 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 To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
