On 2010/05/31 05:04, RICHARD SCHULTHIES wrote: > The mystery may have been solved! If we hear from others that have > the situation, and they also never did the edit, then this might give > the legacy staff a clue where to look for a possible 'bug' that after > a later update, may have left residual problems in databases that > were added to in between the 'wrong' times, that went unnoticed by > everyone. This is very unusual, so the people that met the exact > criteria, were few. I have known of this happening in a different > program, a few years ago. Details unimportant. Hopefully, the staff > will explain, how a person could run a check on their DB, then > furthur explain how to fix it if found. Hopefully, Tuesday afternoon > we should get something. Hopefully they, and you all have a pleasant > holiday (Memorial Day in USA).
I have already posted the reasons! a) Add a person b) Add a child Now check the marriage wording for the person + Unknown. -- Regards, Mike Fry Johannesburg 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
