John, Yes, you have to remember to manually update the User ID's. The time to do it is before any event, such as a GEDCOM import, that may cause existing USer ID's to change. In any case, provided you always check the "Only fill blank user ID's" option, (checked by default, I think) the existing User ID's won't be overwritten. This works, but is error prone.
Still, your idea of having a configurable option so that the RIN is automatically inserted into a blank User ID field when someone is added, seems like a good one to me. It needs to only do it once on initial creation, and I suspect, should not do it on import from GEDCOM, or any other source. Needs a bit of careful design to be robust. Rob On Apr 6, 2005 8:52 AM, John <[EMAIL PROTECTED]> wrote: > Mr. Terry, > > I'm on a "temporary" computer for a few days so I don't have access to > Legacy so forgive me if I am wrong on this. > One caveat: > 1. Use the fill User IDs with RIN option > A. All existing people get their RIN inserted into their > respective UIDs > 2. Add some new people to database > A. New people do NOT have the RIN inserted into the UID field > 3. Perform some action that causes the RIN to change > A, Export to GedCom and import back in to remove empty RINs or > whatever > 4. Now do the fill UID with RIN again to get the _new_ people that > were added in step #2 > 5. And RINs that changed during the import of the GedCom will now > have a different UID > If the above is true, then Legacy would need a means of "locking" the > UID once it was set to prevent change OR > a better solution might be the option to have Legacy automatically > insert RINs as new people are entered so that it would not be necessary > to rerun the fill command from the options menu. > > If I'm talking through my hat on this, please forgive and ignore. > > Cheers, all > > John > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > > JimTerry wrote: > > >Gayle and Karen, > > > >You can make your RIN's permanent by having Legacy copy your RINs into the > >the User ID field. You can also add optional preceding text to the RIN's. > >Click on Options and select Customize > Other and go to the Custom User ID > >Numbers feature. > > > >Once you have done this, use the User ID field because it will have your > >RIN's. It won't change when merging records or renumbering you RINs. This > >isn't a perfect solution, but it's something to consider. > > > >Jim Terry > >Technical Support > >Legacy Family Tree > > > >-----Original Message----- > >From: [EMAIL PROTECTED] > >[mailto:[EMAIL PROTECTED] On Behalf Of Karen > >Sipe > >Sent: Tuesday, April 05, 2005 7:39 AM > >To: [email protected] > >Subject: RE: [LegacyUG] ANother question > > > > > >Gayle, How will you find the documents for an individual when the RIN > >changes? Karen > > > >Legacy User Group Etiquette guidelines can be found at: > >http://www.LegacyFamilyTree.com/Etiquette.asp > > > >To find past messages, please go to our searchable archives at: > >http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ > > > >To unsubscribe please visit: > >http://www.legacyfamilytree.com/LegacyLists.asp > > > > > > > > > > Legacy User Group Etiquette guidelines can be found at: > http://www.LegacyFamilyTree.com/Etiquette.asp > > To find past messages, please go to our searchable archives at: > http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ > > To unsubscribe please visit: > http://www.legacyfamilytree.com/LegacyLists.asp > Legacy User Group Etiquette guidelines can be found at: http://www.LegacyFamilyTree.com/Etiquette.asp To find past messages, please go to our searchable archives at: http://www.mail-archive.com/legacyusergroup%40mail.millenniacorp.com/ To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp
