On Wed, 16 Dec 2009 16:43:09 -0800, [email protected] wrote: >Now let's change the numbers slightly for a second scenario. Suppose I enter a >person that was born in 1908 with no death date information and my auto-death >setting remains at 100. That makes the persons age 101. Legacy does not even >bother asking me about the person because his/her age is MORE THAN the >auto-death setting. But what if the person were still living and out of 50,000 >names in my family file, he is the only person that lived to be older than >100. Bad news, because Legacy will automatically mark him as NOT LIVING. OK, >no problem. On the person's Individual Information window, I can go in an >click on the LIVING-YES button and when I cursor off that line, the setting >seems to stick but when I close the window, it reverts back to LIVING-NO. >There is no way to override when a person's age exceeds the auto-death setting. > >Perhaps I had gotten the mistaken impression that the OP was greeted by that >dialog box I talked about in my first paragraph thus my reason for questioning >why is was not "sticky" for the OP. In the second scenario, it works as you >described and as you state you like the way it works. I also like the fact >that Legacy has such an auto-death setting and will magically go into a >person's family file and "kill off" all those old folk just hanging around for >200 years or more where no death date info was ever entered. But I do have to >state that I should think a user should be able to pick one individual who >happened to outlive everybody's expectations (and the auto-death setting) and >manually set the person as still living and have that override stick. Since >the option to even pick LIVING-YES on such people still exists within the >program, I wonder if the programmer's got it right, that is forgot about >making the manual override stick.
First of all, the only field in the database is tblIR.Living with two values, 0=Yes and 1=No. There is nothing in the database to indicate that the value was set manually. So this tells me that it is working as designed. By setting the dead option to 100, you are telling Legacy to mark the person dead if their age is greater than 100 ... no exceptions. If you want a few exceptions you should set the dead option higher, which is why I set mine to 110. If I should encounter a living person whose age is greater than 110, I will bump it up a few years to compensate. That being said, you are probably correct in stating that Living-Yes should not be selectable if the computed age would make the individual older than the dead option. As I said, I am satisfied with the way it currently works. If you are not happy with the status quo, you should feel free to submit a suggestion to http://www.legacyfamilytree.com/suggest.asp. -- Dennis Kowallek (LTools) http://zippersoftware.com/ltools http://groups.yahoo.com/group/ltools 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
