I do not agree that using RINs sets one up for problems. In fact they form the file names for Pedigree Web Pages and, for me changes would ruin all my search engine references - a disaster as I have spent years getting them established!
The only thing one has to ensure is that the "Reuse abandoned RINs" is unchecked. Naturally, the other precaution to take is always to back-up, but this should be one's standard practice anyhow. RINs do *not* get changed when another person is entered but a new RIN is created, They are *never* changed unless you do it yourself. If meging is carried out properly this has no effect on the RINs. I don't use MRINs, so cannot comment on their stability. Ron Ferguson _____________________________________________________ New Tutorial: Embed Blogger RSS feed into your Website http://www.fergys.co.uk Includes the family tree for Alan J Grimshaw http://www.fergys.co.uk/Grimshaw/ For The Fergusons of N.W. England http://myweb.tiscali.co.uk/fergys/ ____________________________________________________ ---- Original Message ---- From: RICHARD SCHULTHIES To: [email protected] Sent: 22 December 2009 05:08 Subject: Re: [LegacyUG] Question about File ID > My way may not be best, but here is what I do. I have made manila > folders for each Surname. Those that get too full, get split into, > ultimately, individuals with their own folder. I do not put the RINs > or MRINs on the folders at all. When I keypunch using a source, on > the extra photocopies, I put the RINs on them as they are entered. > When I merge people from those later, I do not 'correct' the changes. > Since the main thing for me is that the Sources and notes, show I > have used them to add to my family, and although the RIN changed, the > Source and/or detail didn't. I had one source which duplicates 80% of > over 1500 of my cousins (two censuses in small town in Norway). I > agree with Laura, that using RINs as if permanent, can set oneself up > for disaster. Preserving them, will drive a person nuts. It did to me. > Rich in LA CA > > > > > > > From: Laura Dunwald <[email protected]> > To: [email protected] > Sent: Mon, December 21, 2009 2:30:00 AM > Subject: Re: [LegacyUG] Question about File ID > >  > I should add, that I have found the use of RINs, and MRINs, NOT > HELPFUL! Everything gets messed up as one adds new people, or deletes > duplicates created when more information on an individual is found, > or as was pointed out when new children are found, or when melding > files together, and all the other things one does to mess up the RIN > numbers. > > Laura > ----- Original Message ----- > From: RICHARD SCHULTHIES > To: [email protected] > Sent: Saturday, December 19, 2009 7:56 PM > Subject: Re: [LegacyUG] Question about File ID > > > That is why I left the Dollarhide system (it was good but too > cumbersome). . The ahentafel numbers were over 30-40 characters long. > It was not the only system I used before I bought my first computer, > but when the programs created RINs, I no longer needed to deal with > them anymore. > Rich in LA CA > > > > > From: Heather Stovold <[email protected]> > To: [email protected] > Sent: Sat, December 19, 2009 5:08:13 PM > Subject: Re: [LegacyUG] Question about File ID > > > The main problem I found with the Dollarhide system (which I used > years ago for a while) - is that if you discover a child you didn't > know about that changes the numbers of other people you have already > entered. Also, the numbers can get pretty long, although the longer > the number, the less related the people likely are to you.... > > How have you found this to work with Legacy? Do you give everyone > this number for their ID number? 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 To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
