Great Idea!! I may use that in several places where the maiden name is used where I would prefer to see her married name..... Sometimes the answer is so simple, Less is More.
Thanks On Fri, Sep 6, 2013 at 1:15 PM, Ron Ferguson <[email protected]>wrote: > Kathy, > > Why not just use the wife's first name? Whilst I agree that this is > perhaps not ideal, her married surname can easily be inferred from other > details. > > > Ron Ferguson > http://www.fergys.co.uk/ > > Brian/Support <[email protected]> wrote: > > >I admit at the start that I have not tried this but there is one "rule" > >in the event sentence definition Help that indicates there may be no way > >to have a death notice event for a woman use her married surname. > > > >Here is a quote from the help. > >"Note: Some [fields] are meant to be used for individual events and > >others for marriage events. The fields for marriage events include: > > > >[CoupleFirstNames] > >[HusbFirstName] > >[HusbFullName] > >... any fields beginning with "[Husb" > >[WifeFirstName] > >[WifeFullName] > >... any fields beginning with "[Wife" > >[MRIN] > > > >If these are put into individual events, they would not always make > >sense. For example, using [HusbFullName] in the sentence for a woman > >that was never married, or was married more than once, would not result > >in a name. Legacy can't just remove the field, or leave it unchanged in > >these cases, so it should not be used. When Legacy finds a marriage-type > >name field in an individual event sentence, like [HusbFullName], it just > >returns the current individual's name information...even if that person > >is a female." > > > >[WifeMarriedSurname] is one of the marriage fields not allowed in an > >individual event sentence. By this rule. The married surname of a woman > >is stored with the marriage information for the couple so it is not > >available for use when creating a sentence for an event for the > individual. > > > >Remember that there may be multiple marriages so Legacy would not know > >which marriage to pick as the source for the married surname where a > >person has multiple marriages if we "allowed" marriage type fields with > >individual events. > > > >Brian > >Customer Support > >Millennia Corporation > >[email protected] > >http://www.LegacyFamilyTree.com > >-- > > > >On 04/09/2013 6:50 AM, Kathy Thompson wrote: > >> Sorry to ask yet another question about Sentences, but this one is more > >> about Conditional Formatting within a definition. > >> > >> I have an event "Death Notice" - everyone is likely to have one (no-one > is > >> immortal afterall) > >> Because females typically change their surname at the time of their > >> marriage, death notices are usually published in the married name rather > >> than the maiden name. Males usually don't change their surname. > >> > >> As such, what I want my sentence to do for my Death Notice event is to > >> produce one of two possibilities. > >> For males and unmarried females - use the preferred given name and > surname > >> For married woman - use the preferred given name but use the married > surname > >> > >> As an example... > >> Jane Doe, dies unmarried on 1 Jan 1900, death notice is published on 2 > Jan > >> 1900 in The Newspaper. > >> The sentence should read roughly like > >> On 2 Jan 1900, the death notice for Jane Doe appeared in The Newspaper. > >> (any notes)(sources) > >> > >> However, if Jane Doe had married John Blow at some point, then her death > >> notice sentence should read > >> On 2 Jan 1900, the death notice for Jane Blow appeared in The Newspaper. > >> > >> A male would have the same sentence result regardless of marital status > due > >> to no change of name. > >> > >> I know that there are some Conditional things that can be written in to > the > >> Sentence Definitions (living vs deceased words, buried vs cremated), > but I > >> can't figure out the [:: :: ] combo for this sentence to work. > >> > >> Anyone know how I can achieve this, or am I currently asking too much of > >> the program? > >> > >> Thanks. > >> > >> > >> > >> Legacy User Group guidelines: > >> http://www.LegacyFamilyTree.com/Etiquette.asp > >> Archived messages after Nov. 21 2009: > >> http://www.mail-archive.com/[email protected]/ > >> Archived messages from old mail server - before Nov. 21 2009: > >> http://www.mail-archive.com/[email protected]/ > >> Online technical support: http://www.LegacyFamilyTree.com/Help.asp > >> Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) > and on our blog (http://news.LegacyFamilyTree.com). > >> To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > >> > >> > > > > > > > >Legacy User Group guidelines: > >http://www.LegacyFamilyTree.com/Etiquette.asp > >Archived messages after Nov. 21 2009: > >http://www.mail-archive.com/[email protected]/ > >Archived messages from old mail server - before Nov. 21 2009: > >http://www.mail-archive.com/[email protected]/ > >Online technical support: http://www.LegacyFamilyTree.com/Help.asp > >Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and > on our blog (http://news.LegacyFamilyTree.com). > >To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > > > > > > Legacy User Group guidelines: > http://www.LegacyFamilyTree.com/Etiquette.asp > Archived messages after Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Archived messages from old mail server - before Nov. 21 2009: > http://www.mail-archive.com/[email protected]/ > Online technical support: http://www.LegacyFamilyTree.com/Help.asp > Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and > on our blog (http://news.LegacyFamilyTree.com). > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > > Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
