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
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 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
On 4/16/2014 3:51 PM, Jay 1FamilyTree wrote:
> Since I started running Renumbering both RIN's and MRIN's AND Check
> Repair EVERY day,
>
> I have no longer experienced any inconsistencies or problems with my
> database.
>
> The cleaner and more compact the database file is, the less chance
> there will be unexpected problems.
>
> With over 220,000 persons and over 40,000 media files linked, I
> continue to be thankful for Legacy's overall strength at managing the
> data.
>
>
> On Wed, Apr 16, 2014 at 3:34 PM, Jim Terry/Support
> <[email protected] <mailto:[email protected]>> wrote:
>
> I spoke too soon. After running Check/Repair on my family file and
> resetting the ANcestor Book options I can no longer re-create the
> Events problem.
>
> Jim
> Technical Support
> Legacy Family Tree
>
>
> -------- Original Message --------
> > From: "C.G. Ouimet" <[email protected]
> <mailto:[email protected]>>
> > Sent: Wednesday, April 16, 2014 3:15 PM
> > To: [email protected]
> > Subject: RE: [LegacyUG] Events in Ancestor Book Report misplaced
> >
> > Kinda scary that you might have to watch the reports line by
> line . My daughter's Ancestor Book is ~1600 pages .
> >
> >
> >
> >
> >
> > C.G. Ouimet
> >
> > Kingston ON
> >
> >
> >
> > From: Marnie Oakes [mailto:[email protected]
> <mailto:[email protected]>]
> > Sent: April 16, 2014 06:02 PM
> > To: [email protected]
> > Subject: Re: [LegacyUG] Events in Ancestor Book Report misplaced
> >
> >
> >
> > I reported this issue to support. Jim was able to reproduce the
> problem and has logged it into the "bug" system as "Ancestor Book
> adds spurious Events to individuals". Thanks, Jim.
> > Marnie
> >
> >
> >
> > On 4/14/2014 11:36 PM, Marnie Oakes wrote:
> >
> > I completed a 12 generation ancestor report and started checking
> through it. All seems well until close to the end. Then I start
> getting individuals, who have no events attached to them in the
> database, but with events that belong to other people. Here is
> an example:
> >
> > 1856. Phillip Fowler,263 son of ____________ ____________ and
> ____________ ____________.
> >
> > Phillip married someone. ____________ ____________
> >
> > Noted events in his life were: [These events come from other
> lines in my fdb, not from the one I was documenting in the
> Ancestor Book. They all appear to be shared events.]
> >
> > . was a Mother to the Census of George C. Cook 1900
> Walkerton, Lincoln township, St. Joseph, Indiana.289
> >
> > . George was the head of household in the census of Harold E.
> Reynolds in 1910 in Yonkers, Westchester, New York, United States.
> [Not related to George above]
> >
> > . Harold was a Wife to the Census of Harold E. Reynolds 1910
> Yonkers, Westchester, New York, United States. [not related to
> Harold below and why he shows as a wife I don't know]
> >
> > . Harold was the head of household in the census of Ruth
> Kneeland in 1930 in Cambridge, Lamoille, Vermont, United States.290
> >
> >
>
>
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
