John, you have gone some way to solving this riddle.  It is not the 'Wording 
Override' but 'Wording Options' tab that has (Person's name) married someone 
(Person's name).  I just checked my apparently isolated situation of the 
superfluous 'someone' appearing in reports.  Other marriages in the 'Wording 
Options' tab have (Person's name) married (Person's name).  This can be changed 
by the user - but I know with 110% certainty that I did NOT manually make the 
change.  It does provide a means of clearing the 'someone' from reports - but 
still begs the question as to how why it got there in the first place.

Cheers
Jan
-----Original Message-----
From: John & Elizabeth Pethybridge [mailto:[email protected]]
Sent: Sunday, 30 May 2010 20:02
To: [email protected]
Subject: Re: [LegacyUG] Ancestors Report Help - current build 7.4.0.39

Ron
I was referring to the Build Date as sometimes still under the cover of the
latest version there can be subtle programming changes with a different
edition as described by the Build Date. Thought that you may have a later
Build Date that has been "experimented with".

All the Defaults are set correctly but that is not the problem as Legacy
offers the option to edit individual Marriage Wording in the Tab "Wording
Options" at the top of the "Marriage Information" window. To get the effect
of the "fault" you have to follow the previously described routine for data
entry exactly.

What changes is the entry behind the Tab as described i.e. "Wording
Override". Opening the Tab will show that an Override of "Married Someone"
has been set as though it was intended to be that way, irrespective of the
"Default" Settings in Options>Customise>View> Edit Default Marriage
settings.
It matters not that it is a Desc. or Anc. report as it is set in the
Marriage just for that couple by the data entry update process. It would not
matter that one Spouse was entered as a line or alpha, just that there was a
RIN allocated. If no RIN I bet it would always show "Married someone".
I have not tested if a there is an entry type that does not get a RIN.
John





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

To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp



Reply via email to