Hoping that the Legacy programmers fix the file importing and merging problems. I lost a lot of info on an import from another copy of my Legacy data a while ago. Appeared to lose Ancestry numbers, etc. Following your recommendations might have helped, but it should not be necessary. I detest the large numbers used by FS, and have tried to eliminate them when doing merges!
On a related topic, I still say, as I said years ago, the Source data should be one of the clickable tabs when doing merges! We should be able to see the sources and select the ones we want to save or combine when merging> Jay Ingalls ========================================== Subject: Re: [LegacyUG] Events in Ancestor Book Report misplaced Date: Wed, 16 Apr 2014 17:46:41 -0700 From: JV Leavitt <jleavi...@att.net> Reply-To: legacyusergroup@LegacyUsers.com To: legacyusergroup@LegacyUsers.com Yea! I'm glad to see that at least one other person has discovered that if you are doing a lot of work on your database, the practice that Jay [not Jay Ingalls] describes will help make your life a happier one than you might otherwise have been able to enjoy. My largest file is 167,000 records, and the most difficult of operations was to merge a small section back into it after it had been expanded, optimized, and sync'd with FS FT. I supposed that an AutoMerge using IntelliShare ID numbers would be all that was needed. Not so. There are new issues now, having to do with FSID's being lost in the process, for one thing. I learned from others on this list to have the small file come in with very large RIN numbers. I switch them right away to the left side of the merge window, and proceed one by one. A confusion factor would appear if I had allowed abandoned RINs to be reused (Customize 4.4) -- it seemed to cause serious problems in the merge process, but this was only a suspicion of mine, and not proved by testing, etc. Before doing such a merge, I learned to first renumber RINs and MRINs, and a few other preparatory steps I worked out, like backing up first (duh...), and to run the first three file maintenance options on both files, and to make no other changes before starting the merge. My merge operations are coming out clean now, and without difficulty or problems of any kind. I too am thankful for "Legacy's overall strength at managing the data." Afterthought -- Okay, here are the steps I worked out: *Before Merge -- of the Master File and the small file to be merged * Backup both files Search and Replace -- Location Names & Short Loc. Names (, United States), both files Combine duplicate location names Renumber RINs & MRINs on both files File Maintenance - First three options on both files Refresh and print tree list for Master File *Merge Operation* All records - pertains to the imported file *Renumber RINs from 200001 * - pertains to the imported file. (*Do not renumber from 1*, as this is already being used by the Master File *Do not* Fill all existing abandoned RINs/MRINs AutoBackup option not necessary -- done in a previous step At beginning, when location differences are shown: Keep / transfer GPS data onto left side Keep / transfer best location names onto left side *At first merge window, swap to have large RINs on left side – necessary to keep FSIDs * **(_*None of the imported sync data from FS FT is kept unless it is on the left side*_) RINs of imported [FS] file are large, this makes merge data easier to see Watch out – the program will call out possible merge of children with same name where one died young, but another was born later with the same name Watch out – names of spouses might be slightly different – might need to make them the same Do not use AutoMerge - IntelliiShare options *After Merge -- Master file * Backup – before any corrections etc. File Maintenance, First three options Renumber RINs & MRINs Set relationships Refresh and print trees list, and compare with the one made before the merge Do global sort of child and marriage lists New backup *After Merge – Small File * Rename the small file to move it to the Archive folder. NOTE: Now is a good time to export a small file if one is ready, because the MF is clean. Joseph Leavitt Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ 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
