The robustness would have to include this. If the RIN changes and then you
add the old RIN for a new person. Then you could have duplicate User IDs.
Foxy
----Original Message Follows----
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.
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
