Count me in as one who doesn't see the need for alternate name list 8-)
Yes, I do have variations in spelling, but I know what those are and can
keep an eye out for them when I'm entering a new person or perusing the
name list. I only have a couple of people who truly have AKAs. The detail
tab in the name list can be set to have AKAs showing and you can easily do
a search for a known AKAs in the search feature. That brings up the person
as listed in the name list. I did a quick search of Individual > alt given
name > not equal to > and left the last box blank AND individual > alt last
name > not equal to > (last box left blank) and came up with a list of 5
individuals who had names in the AKA fields. And with the detail tab
showing AKAs, I was able to quickly see not only *who* had AKAs but what
the AKAs were.
If I have an isolated case of uncertain name I'll generally put that name
in the name field with a slash between the two choices.
When entering a new person, there's auto complete and a drop down list for
the surname but not for the first name. I guess I don't understand where
name checking would go beyond that?
Of course, I realize some people have really massive files (my main one has
only 1688 names). How *do* they go back that many generations???? I'm
lucky to be back 7 generations, let alone 35 or more 8-) Maybe the further
back you go the screwier names get?
Sherry
*+*+*+**+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*+*
On 10/22/00 at 10:04 AM John Shaw wrote:
>Jan / LeAnn
<snip>
>The alternate name on the name list is something I and a few others have
>been grumbling about for well over a year. Apparently most other users
>either don't use the alternate name feature or don't care that they cannot
>locate them again without a major hassle.
>
>Quick access to the alternate names is, it would seem, vital since Legacy
>does no name-checking during data entry as some other programs do. As a
>consequence, it becomes very easy to enter duplicates that must then be
>tracked down and merged/deleted.
