I have changed RINs in the past, and ALL data for the person transfered 'moved with' to the new RIN, exactly. My example, when I merged a person (more than one instance) having the wrong choice on the left, making the higher number retained. I used the tool to change the number, I found the program had fixed my mistake. The AKAs were not affected. These were done during L5 and L6. I 'thankfully' haven't done the mis-merge lately, so if there is a programming error, I hadn't seen it. I may be misunderstanding what had actually been done during the RIN change. Rich in LA CA
--- On Sun, 9/28/08, Steve Voght <[EMAIL PROTECTED]> wrote: > From: Steve Voght <[EMAIL PROTECTED]> > Subject: Re: [LegacyUG] Problem Changing RINs > To: LegacyUserGroup@legacyfamilytree.com > Date: Sunday, September 28, 2008, 11:51 AM > I think almost everyone is missing what the problem is that > Carol is > reporting. She understands what the double-S (officially > "section > mark" -- see > http://en.wikipedia.org/wiki/Section_mark) is for, but > according to her most recent post, the problem is the AKAs > are being > associated with the *wrong individuals* after she changed > people's > RINs. > > Thus, if RIN#1 was formerly Jane Smith a.k.a. Jane Smythe > and RIN#2 > was Frank Jones a.k.a. Fred Jones; after Carol changed the > RINs and > swapped their numbers, now RIN#1 is Frank Jones a.k.a. Jane > Smythe, > and RIN#2 is Jane Smith a.k.a. Fred Jones. > > So the base problem is that her AKAs did not get reassigned > properly > and are now all associated with the wrong people. Thus it > sounds like > the only fix (until this bug (?) is fixed) is to go through > every > individual with an AKA, manually delete them, and reassign > them to the > correct individual. This is obviously not an ideal > solution since it > will require a lot of manual labor and re-adding sources > and so > forth... > > Because I've never changed RINs after they are assigned > I can't verify > if this actually is a bug, but it sounds like something to > look out > for if you do consider a mass-reassignment of > identification numbers. > (And as always before doing something major like this, make > sure your > backup is up-to-date!) > > Cheers, > Steve Voght > Seattle, WA > > On Sun, Sep 28, 2008 at 11:13 AM, RICHARD SCHULTHIES > <[EMAIL PROTECTED]> wrote: > > The "double S" is only a computer generated > 'warning' that this is a person who has an AKA in > use, and you currently have the 'show AKAs' turned > on. > > Changing the RIN will only cause the mark to carry > itself to the new RIN. > > Rich in LA CA > > > > --- On Sun, 9/28/08, [EMAIL PROTECTED] > <[EMAIL PROTECTED]> wrote: > > > >> From: [EMAIL PROTECTED] > <[EMAIL PROTECTED]> > >> Subject: RE: [LegacyUG] Problem Changing RINs > >> To: LegacyUserGroup@legacyfamilytree.com > >> Cc: [EMAIL PROTECTED] > >> Date: Sunday, September 28, 2008, 10:33 AM > >> Hi Pauline, > >> > >> I understand about the "double S" for > the name of > >> married women, but this is > >> not the problem. What happened is that it kept > the married > >> names of women > >> RIN, and now they become associated with the > person with > >> the changed RIN. > >> > >> This is probably an indexing problem when changing > RIN? > >> That is when you > >> change the RIN to a number of a female with a > married name > >> RIN. The RIN is > >> not changed with the "double S" > >> > >> Hope this explanation makes sense? > >> > >> Carol > >> > >> > >> -----Original Message----- > >> From: [EMAIL PROTECTED] > >> > [mailto:[EMAIL PROTECTED] On > >> Behalf Of Pauline B. > >> Cramer > >> Sent: Saturday, September 27, 2008 1:51 PM > >> To: LegacyUserGroup@legacyfamilytree.com > >> Subject: Re: [LegacyUG] Problem Changing RINs > >> > >> Carol, > >> > >> If you click on the Index tab, all you have to do > to get > >> rid of the > >> "RINs with the "double S" prefix is > to go to > >> the Options button in the > >> upper right corner and click to turn off the > "Include > >> Married Names" > >> options. What you are calling bogus names should > be the > >> married names of > >> women. This is not a bug, it is a feature. > >> > >> This feature enables you to find a married woman > by looking > >> for her > >> married surname or maiden name, whichever you > remember. It > >> is especially > >> useful for women who have been married two or > three times. > >> It can help > >> you avoid entering two or three records for the > same > >> individual. The > >> names with the squiggle in front of the names are > the AKAs. > >> You can get > >> rid of them from the Index by unchecking the > "Include > >> Alternate Names" > >> in Options. > >> > >> All the names that come up associated with one > single > >> unique RIN number > >> should be the preferred name for that individual > or else > >> that > >> individual's married name or alternate name > for that > >> individual. > >> > >> If that is not the case, then, when you started > changing > >> RINs, you may > >> have inadvertently merged records for two > individuals > >> without meaning to > >> do so. You may have manually entered RIN numbers > that were > >> already used > >> for other existing individuals in the Legacy > family file. > >> What you are > >> calling a bogus name may be the name for another > individual > >> that was > >> already in the database. > >> > >> Pauline > >> > >> [EMAIL PROTECTED] wrote: > >> > > >> > Hi, > >> > > >> > The real problem is how do I remove those > with the > >> same RIN as the > >> > desired person??? The ones which are bogus > have a > >> "double S" prefix. > >> > > >> > I am looking for help on fixing the problem. > Maybe the > >> Legacy support > >> > team will take a look at my problem. It > appears to be > >> a program bug?? > >> > > >> > Carol > >> > > >> > > >> > ------------------------------------------------------------------------ > >> > > >> > *From:* > [EMAIL PROTECTED] > >> > > [mailto:[EMAIL PROTECTED] > >> *On Behalf Of > >> > *Johnny V > >> > *Sent:* Friday, September 26, 2008 5:34 PM > >> > *To:* LegacyUserGroup@legacyfamilytree.com > >> > *Subject:* Re: [LegacyUG] Problem Changing > RINs > >> > > >> > Carol, > >> > > >> > It puzzles me why Legacy even has this > feature. Since > >> Legacy is a > >> > relational database, an RIN is nothing more > than a > >> *_R_*ecord > >> > *_I_*dentification *_N_*umber instructing the > database > >> where to find a > >> > specific record and what records to relate it > to. > >> Changing an RIN is > >> > not something that should be done - period. > >> > > >> > Just my 2ยข worth > >> > > >> > John Valencic > >> > > >> > On 9/26/08, *ronald ferguson* > <[EMAIL PROTECTED] > >> > <mailto:[EMAIL PROTECTED]>> wrote: > >> > > >> > > >> > Carol, > >> > > >> > I do not know what you mean by "the > pedigree > >> numbering system", > >> > something I'm afraid I've never heard > of. RINs > >> are allocated in the > >> > order in which individuals are added to the > database > >> and I have mine > >> > set not to reuse epmty numbers. I have never > changed a > >> RIN and have no > >> > intention of doing so since the RINs are used > as the > >> file names for > >> > pedigree web pages which happen to be my main > >> interest. In any event > >> > any order which might be set will soon be > messed up as > >> other names are > >> > added. > >> > > >> > I think what you mean by muddled/duplicate > numbers in > >> the Index View > >> > is because you have it set to show alternate > names and > >> alternate > >> > married names, these have the same RIN as the > main > >> name for the > >> > individual, as they are one and the same > persons. > >> > > >> > > >> > Ron Ferguson > >> > > >> > > >> > _____________________________________________________________________ > >> > > >> > *New* Insert Pictures Into your Web Pages - > Blogs > >> > http://www.fergys.co.uk > >> > View the Grimshaw Family Tree at: > >> > http://www.fergys.co.uk/Grimshaw/ > >> > For The Fergusons of N.W. England See: > >> > http://myweb.tiscali.co.uk/fergys/ > >> > > >> > _____________________________________________________________________ > >> > > >> > > >> > > >> > > >> > > From: [EMAIL PROTECTED] > >> <mailto:[EMAIL PROTECTED]> > >> > > To: LegacyUserGroup@legacyfamilytree.com > >> > > <mailto:LegacyUserGroup@legacyfamilytree.com> > >> > > Subject: [LegacyUG] Problem Changing > RINs > >> > > Date: Fri, 26 Sep 2008 16:35:54 -0700 > >> > > > >> > > Hi, > >> > > > >> > > Just started to change the RINs so they > match the > >> pedigree numbering > >> > system, > >> > > and found a problem getting other > individuals > >> with the changed number. > >> > > Several persons who RIN was change has > other > >> names with the same > >> > number as > >> > > seen in the Index view. When you > high-light the > >> bogus name and try to > >> > view > >> > > its Family view, it doesn't go to > that name > >> but the person I assigned to > >> > > number. The bogus name starts with a > double S > >> symbol, but lists the > >> vital > >> > > data of the person I assigned the number > to. > >> > > > >> > > I tried all the file maintenance, but > didn't > >> fix the problem. I have the > >> > > latest version of the program, and use > XP. > >> > > > >> > > Any suggestions would be greatly > appreciated. > >> > > > >> > > Carol > >> > > > >> > > > >> > > >> > > >> > _________________________________________________________________ > >> > Make a mini you and download it into Windows > Live > >> Messenger > >> > > http://clk.atdmt.com/UKM/go/111354029/direct/01/ > >> > > >> > > >> > Legacy User Group guidelines: > >> > http://www.LegacyFamilyTree.com/Etiquette.asp > >> > Archived messages: > >> > > >> > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > >> > Online technical support: > >> http://www.LegacyFamilyTree.com/Help.asp > >> > To unsubscribe: > >> http://www.LegacyFamilyTree.com/LegacyLists.asp > >> > > >> > > >> > > >> > > >> > > >> > -- > >> > Talk to you soon > >> > Johnny V > >> > > >> > Legacy User Group guidelines: > >> > http://www.LegacyFamilyTree.com/Etiquette.asp > >> > Archived messages: > >> > > >> > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > >> > Online technical support: > >> http://www.LegacyFamilyTree.com/Help.asp > >> > To unsubscribe: > >> http://www.LegacyFamilyTree.com/LegacyLists.asp > >> > > >> > Legacy User Group guidelines: > >> > http://www.LegacyFamilyTree.com/Etiquette.asp > >> > Archived messages: > >> > > >> > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > >> > Online technical support: > >> http://www.LegacyFamilyTree.com/Help.asp > >> > To unsubscribe: > >> http://www.LegacyFamilyTree.com/LegacyLists.asp > >> > > >> > >> > >> > >> Legacy User Group guidelines: > >> http://www.LegacyFamilyTree.com/Etiquette.asp > >> Archived messages: > >> > >> > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > >> Online technical support: > >> http://www.LegacyFamilyTree.com/Help.asp > >> To unsubscribe: > >> http://www.LegacyFamilyTree.com/LegacyLists.asp > >> > >> > >> > >> > >> > >> > >> > >> Legacy User Group guidelines: > >> http://www.LegacyFamilyTree.com/Etiquette.asp > >> Archived messages: > >> > >> > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > >> Online technical support: > >> http://www.LegacyFamilyTree.com/Help.asp > >> To unsubscribe: > >> http://www.LegacyFamilyTree.com/LegacyLists.asp > > > > > > > > Legacy User Group guidelines: > > http://www.LegacyFamilyTree.com/Etiquette.asp > > Archived messages: > > > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > > Online technical support: > http://www.LegacyFamilyTree.com/Help.asp > > To unsubscribe: > http://www.LegacyFamilyTree.com/LegacyLists.asp > > > > > > > > > > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages: > > http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ > Online technical support: > http://www.LegacyFamilyTree.com/Help.asp > To unsubscribe: > http://www.LegacyFamilyTree.com/LegacyLists.asp Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
