Since my situations of changing unknowns to knowns, were solved back in L5, when I had to repair it myself. I didn't know L7 had fixed it. I in L5, removed all my unknowns, because the program installed the word unknown (in the screen only, not reports) which was what I had been wanting to have done. So, I did it the old way, and will never again put the name unknown for anyone. Let the program do field fills for the screen. Rich in LA CA
--- On Wed, 5/19/10, CE Wood <wood...@msn.com> wrote: > From: CE Wood <wood...@msn.com> > Subject: RE: [LegacyUG] Married 'Someone' > To: LegacyUserGroup@LegacyUsers.com > Date: Wednesday, May 19, 2010, 9:57 PM > I think she is asking why the program > doesn't correct its mistake. As one gathers more > information, there will always be spouses discovered. > There needs to be a string that automatically removes the > "someone" when an actual name is entered. > > Correcting one marriage is not the issue. Correcting > them ALL is ridiculous. > > Legacy did say this error had been fixed. I guess > not, huh? > > > CE > > > -----Original Message----- > From: Jennifer Crockett [mailto:jcrock...@optusnet.com.au] > Sent: Wednesday, May 19, 2010 4:30 PM > To: LegacyUserGroup@LegacyUsers.com > Subject: RE: [LegacyUG] Married 'Someone' > > I once had this happen to me. What I finally came up with > to fix it was to unlink the couple and then re-link them. I > did this using the Marriage List. > > Jennifer > > > From: Jan Roberts [mailto:poo...@ozemail.com.au] > Sent: Thursday, 20 May 2010 9:18 AM > To: LegacyUserGroup@legacyusers.com > Subject: [LegacyUG] Married 'Someone' > > I have just been reading through a report I created > yesterday (after having converted pdf to doc, edited – or > so I thought – resaved as pdf, uploaded to my newly > created wiki!) and have noticed that I have the ubiquitous > Fred married someone Mary Jane BROWN. I thought this > problem had been resolved some time ago. Originally I > had an unknown wife for Fred, but recently added a > name. Obviously the someone is a hangover from when > her name was unknown. How does one resolve this > problem other than having to read through every report word > for word once it has been created. At the moment I > tend to rely on Word’s spelling error identifier to check > for spelling errors, as well as making any additions or > deletions that I know I need – I’d prefer not to have to > check the wording of every marriage statement just in case > the extraneous ‘someone’ is in place. > > Cheers > Jan > > > > > > Legacy User Group guidelines: > > http://www.LegacyFamilyTree.com/Etiquette.asp > > Archived messages after Nov. 21 2009: > > http://www.mail-archive.com/legacyusergroup@legacyusers.com/ > > Archived messages from old mail server - before Nov. 21 > 2009: > > http://www.mail-archive.com/legacyusergr...@legacyfamilytree.com/ > > Online technical support: http://www.LegacyFamilyTree.com/Help.asp > > To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp > > > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 9.0.819 / Virus Database: 271.1.1/2868 - Release > Date: 05/18/10 11:26:00 > > > > > Legacy User Group guidelines: > > http://www.LegacyFamilyTree.com/Etiquette.asp > > Archived messages after Nov. 21 2009: > > http://www.mail-archive.com/legacyusergroup@legacyusers.com/ > > Archived messages from old mail server - before Nov. 21 > 2009: > > http://www.mail-archive.com/legacyusergr...@legacyfamilytree.com/ > > Online technical support: http://www.LegacyFamilyTree.com/Help.asp > > 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/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergr...@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
