>I'm not suggesting automatic merging of names, you're right, no one would >be happy with automatic combinations. > >I'm only suggesting that the secondary db name data be placed into a NOTE >rather than being discarded as is the case now. I will add some of these ideas to my list and see how things go. Sometimes they get added later than sooner - depends on difficulty, etc. of implementation. >>I think the Rebuild problem is related to the multiple marriage problem. >>When the marriages don't get set correctly, the Rebuild attempts to repair >>them. >Premature rebuilding was the source of most of my db merge problems. >The program's advice to rebuild immediately after a merge is misleading and >perhaps should be rephrased., I think that if the DB merge works properly - as it should - then the Rebuild won't cause the problems you are having here. I need to concentrate on the Merge bugs. Ira ------------------------------------------------ Mr. Ira J. Lund E-mail: [email protected] Web: http://www.cf-software.com Cumberland Family Software, 385 Idaho Springs Road, Clarksville TN 37043