I would like to "ditto" this. The issue has bit me several times, that I know of ... don't know how many bads are still out there!
This thread also leads to the issue of a tag to assign a type, if you will, to the AKA. We document many different types of AKA's. For example, nicknames, legal surname changes, preferred or commonly used given names, simple misspellings or documentation errors, name "Americanization", and probably others. Because of Norwegian patronyms and names changing as folks relocated in Norway, I have many AKA's documented simply to be able to see alternative possibilities in the Name Lists. They really look clunky when they show up in a report. I would like to see in future versions an ability to assign a tag to the AKA and then be able to apply report options to use or not use AKA's by type. Thanks, Don Cook ----- Original Message ----- From: "Ruth" <[EMAIL PROTECTED]> Subject: [LegacyUG] Sourcing AKAs Just a small plea to change the AKA functionality slightly. When you save a new AKA, the first AKA in the list is highlighted rather than the new AKA. As I always source my new AKA straight after entering it I often find myself sourcing this top one rather than the one I've just entered. Can anyone think of a reason why the new AKA should not be highlighted once saved? 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
