I wrote yesterday regarding duplicate entries. I got several responses all of which said that basically the method outlines on p.67 is the only way to deal with it. (Decide which one you want to keep; copy all info over from the other; then delete the other.) I do this - but generally I rename the 'deleted' one "John deleted Smith", so it is still there just in case I make a mistook. However, two other possibilities have occurred to me: 1. Can I export GEDCOMs for the two relevant items; then edit the GEDCOMs in some clever way (I don;t know how); then import the GEDCOM which will give just one individual obatined by merging the other two. 2. Would it be possible in future to have an "Is identical to" relation? This would keep them as two records but would regard them as one individual. Any comments please on the feasibility of the above? JOHN B

John Bibby wrote: > 2. Would it be possible in future to have an "Is identical to" > relation? This would keep them as two records but would regard them as > one individual. > > Any comments please on the feasibility of the above? John, Would you remember to update both entries if you found new information? I'm afraid I wouldn't, and then it would just get more messy/confusing from there. Mona -- Mona Houser HeritageHunt@Sandyview.net Our Family -- http://freepages.genealogy.rootsweb.com/~monajo/ Nahausen Families – http://freepages.genealogy.rootsweb.com/~monajo/nah/ My Database – http://wc.rootsweb.com/~monahouser