Bill, Another option is to import the dubious file into a new, empty Legacy file, master sourcing all data to the compiler's information and forcing RINs to a number range well outside anything in your existing file and where it might grow to, e.g. commencing at 5,000 or above. Then make a copy of your family file and rename it to indicate a work file status. Merge the dubious file into the work file. You then have a file where you can readily evaluate and research potential relationships, but where UID identification and RINs for your family file are preserved, permitting Intellishare to be used if and when you have enough to do a partial or full merge back to your family file. There's little chance of confusion with this approach, and Legacy has numerous ways to help you keep clear what you have, have done, and plan to do.
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 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
