Dennis,
I actually presented the AKA type approach in a reply to Sherry about an
hour ago. In looking at my Sent Items box, I now see that it went only
to her.
I agree that if this could be done it would be the ideal approach to the
issue and present several other opportunities to the developers as you
have pointed out. We have seen many postings pertaining to handling of
Nicknames and Marreid vs. Maiden names, for example.
Don
----- Original Message -----
From: "Dennis Kowallek" <[EMAIL PROTECTED]>
On Wed, 26 Apr 2006 12:19:54 -0600, "Don Cook" <[EMAIL PROTECTED]> wrote:
For purposes of this discussion, I have two types of AKAs:
1) Those I want to appear in reports.
2) Those I DON'T want to appear in reports.
I guess what I was getting at is the concept of assigning an AKA Type to
each AKA. Then having the print/noprint attribute be associated with the
Type. Of course, if it was designed flexibly, you might simply choose to
create just two Types of "Print" and "Don't Print". Maybe Legacy would
even make these the two built-in Types with "Print" as the default.
You could take the concept of an AKA Type further by allowing the user
to assign different sentence structures to different Types. Maybe a
"Nickname" type would be associated with the sentence "[He/She] went by
the nickname of [AKA]." Etc.
Any other ideas?
--
Enter the drawing for a FREE Legacy Cruise to Alaska or a FREE research trip to
Salt Lake's Family History Library. Open to users of Legacy 6 Deluxe. Enter
online at http://legacyfamilytree.com/FreeTrip.asp
Legacy User Group 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/
For online technical support, please visit
http://www.legacyfamilytree.com/Help.asp
To unsubscribe please visit: http://www.legacyfamilytree.com/LegacyLists.asp
