Here is why it says that. You may find after adding file B to file A that there were 'bad' locations and 'undesirable' alternate spellings of places and names. What I do, is FIX the new file completely, then import to the old one. The main concern is that after adding both files together it is harder to look through for undesirable data. This can also be fixed by using new named backups. It is basically for your protection. >From one who shoude have done it. Rich
--- [EMAIL PROTECTED] wrote: > I think the directions in the instruction manual > and the pop-up prompts are > incomplete on this. > > When you want to merge two Legacy files by using > the Import command, the > prompt encourages you to create a third file. When > you do this, all that > happens is that the incoming file goes into that > third file. Then you have to go > back and do a separate import of your original > file. You'd think they'd put > both of the original files into the third file in > one step. > > Maybe it's something they overlooked? There is no > added safety by making it > a two-step process. > > > > Legacy User Group guidelines can be found at: > http://www.LegacyFamilyTree.com/Etiquette.asp > > To find past messages, please go to our searchable > archives at: > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > > For online technical support, please visit > http://www.LegacyFamilyTree.com/Help.asp > > To unsubscribe please visit: > http://www.LegacyFamilyTree.com/LegacyLists.asp > Legacy User Group guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp To find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ For online technical support, please visit http://www.LegacyFamilyTree.com/Help.asp To unsubscribe please visit: http://www.LegacyFamilyTree.com/LegacyLists.asp
