Re: [LegacyUG] Help with Living/Non-Living

[Wynthner]

There can be a great downside to those sent a GEDCOM with non-dates in a date 
field; depending on the importing program it may or may not transfer that 
non-date data and thus, depending on the preferences of the person recieving 
the data, have to be removed by the recieving party.
I personally loath those type of entries. In fact, I consider using data fields 
for info other than that which they were meant for to be one of the Cardinal 
Sins of Data Entry.


- Original Message 
From: Mary Young <[EMAIL PROTECTED]>
To: LegacyUserGroup@legacyfamilytree.com
Sent: Monday, June 2, 2008 7:26:04 AM
Subject: Re: [LegacyUG] Help with Living/Non-Living

On 6/2/08, Cathy <[EMAIL PROTECTED]> wrote:
>  I don't advocate putting non-dates in date fields.
Cathy, why not? Is there a downside to putting "unknown" in a date field?
-- 
Mary Young







Legacy User Group guidelines:
   http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages:
   http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp

Re: [LegacyUG] Help with Living/Non-Living

[Cathy]

Hi Mary,

I prefer blanks for unknowns. If nothing is entered it is clearly unknown.

You also then have the option of creating a report with underlines 
for unknown dates and places to send to people who may know and be 
able to fill in some blanks.


If you do enter a non-date, you'll need to exempt them from Potential problems.

Cathy

At 08:26 PM 2/06/2008, you wrote:

On 6/2/08, Cathy <[EMAIL PROTECTED]> wrote:
>  I don't advocate putting non-dates in date fields.
Cathy, why not? Is there a downside to putting "unknown" in a date field?
--
Mary Young





Legacy User Group guidelines: 
  http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages: 
  http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

Online technical support: http://www.LegacyFamilyTree.com/Help.asp
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp

Re: [LegacyUG] Help with Living/Non-Living

[Mary Young]

On 6/2/08, Cathy <[EMAIL PROTECTED]> wrote:
>  I don't advocate putting non-dates in date fields.
Cathy, why not? Is there a downside to putting "unknown" in a date field?
-- 
Mary Young



Legacy User Group guidelines: 
   http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages: 
   http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp

Re: [LegacyUG] Help with Living/Non-Living

[Cathy]

Hi Carol,

Others have alerted you to the Advanced Set Living tool - this is a 
deluxe feature.


In Options > Customise you can change the default setting for the 
Living flag. See the Data Defaults tab.
I prefer to leave it set to default to Living as I don't want to 
inadvertently set Living people to dead and risk exporting data on 
living people.


I don't advocate putting non-dates in date fields.

Legacy doesn't give you an immediate pop up that you may be adding a 
duplicate. It does have a good find duplicates routine, but that's 
after the fact of entry. No change in this for version 7.


Cathy

At 05:37 AM 2/06/2008, you wrote:
Many times, a research document may show the names of children, but 
not give the birth/death dates. I had 65,000 names when I 
transferred by database from FTM to Legacy. Now, on Legacy,I find 
this wonderful little button that allows me to show whether the 
person is living or dead.


I'm finding in my transferred data that "non-dated" children of 
parents who m. back in the 1700s, are showing as "living". Several 
questions: Do I need to go back and change each one using the Legacy 
button to show "not living"? In the future, should I just record 
"yes" in the death date area if I know the person has died, but have 
no dates? (I could not do this on FTM).


Also, it's interesting to find that there is no software check on a 
wife with no dates, who married a man with birth/death dates back in 
the 1600-1700s. The husband can show as "not living", but if there's 
no marriage date, then the wife shows as living. Again, I'm 
correcting all these one-by-one.


One additional small thing I miss in FTM is the ease with which they 
had an alert on possible duplicates. I don't find that Legacy 
catches duplicates very easily. Maybe these things will change in 
the new version.


Carol





Legacy User Group guidelines: 
  http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages: 
  http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

Online technical support: http://www.LegacyFamilyTree.com/Help.asp
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp

Re: [LegacyUG] Help with Living/Non-Living

[Bob Withers]

Carol,

On the Tools menu look at Advanced Set Living...

Regards,
Bob

On Jun 1, 2008, at 4:37 PM, [EMAIL PROTECTED] wrote:

Many times, a research document may show the names of children, but  
not give the birth/death dates. I had 65,000 names when I  
transferred by database from FTM to Legacy. Now, on Legacy,I find  
this wonderful little button that allows me to show whether the  
person is living or dead.


I'm finding in my transferred data that "non-dated" children of  
parents who m. back in the 1700s, are showing as "living". Several  
questions: Do I need to go back and change each one using the Legacy  
button to show "not living"? In the future, should I just record  
"yes" in the death date area if I know the person has died, but have  
no dates? (I could not do this on FTM).


Also, it's interesting to find that there is no software check on a  
wife with no dates, who married a man with birth/death dates back in  
the 1600-1700s. The husband can show as "not living", but if there's  
no marriage date, then the wife shows as living. Again, I'm  
correcting all these one-by-one.


One additional small thing I miss in FTM is the ease with which they  
had an alert on possible duplicates. I don't find that Legacy  
catches duplicates very easily. Maybe these things will change in  
the new version.

Re: [LegacyUG] Help with Living/Non-Living

[Dawn Crowley]

Perhaps this information from the help screen answers your question:

Advanced Set Living







There are several Legacy reports, plus web pages, where the privacy of 
anyone whose Living status is set to Yes is protected by suppressing all 
personal details.  When creating these reports, no information is 
included for ancestors born centuries ago if they are inadvertenly left 
set as Living.




Normally an individual's Living status is set at the time they are 
manually entered.  The process is automatic if their death or burial 
information is entered or their birth or christening date is more than 
120 years ago.  If no birth, christening, death, or burial information 
is entered, their status remains at the default Yes, if not changed to No.




It is an easy task to set the Living status of a few individuals 
manually, but the task can become formidible when adding hundreds or 
thousands of new people to your family file with a GEDCOM import.  This 
is where the Advanced Set Living feature comes in handy.  This option 
does an intelligent search through your entire family file looking for 
people that are are older than the cutoff age, which is usually 120 
years old.  When someone of this age is found, it is assumed that all of 
their ancestors are older than that and that they are all dead.  Legacy 
then sets their Living flag to NO as far back as the line goes from 
there, regardless of whether or not they have birth or christening dates.




To use the Advanced Set Living feature:



1. Choose Advanced Set Living from the Tools menu.

2. Set the cutoff age at the desired level by either typing in the 
number or by using the up and down arrows of the spin control.


3. Click the Start button.  Legacy goes through your entire family file 
setting the Living flag to NO when it is determined that they are older 
than the you specified.  When finished, Legacy asks if you would like to 
see a list of all the people who had their Living flag set to NO.  To 
view the list, click Yes.  




6-139




[EMAIL PROTECTED] wrote:

Many times, a research document may show the names of children, but 
not give the birth/death dates. I had 65,000 names when I transferred 
by database from FTM to Legacy. Now, on Legacy,I find this wonderful 
little button that allows me to show whether the person is living or 
dead.
 
I'm finding in my transferred data that "non-dated" children of 
parents who m. back in the 1700s, are showing as "living". Several 
questions: Do I need to go back and change each one using the Legacy 
button to show "not living"? In the future, should I just record "yes" 
in the death date area if I know the person has died, but have no 
dates? (I could not do this on FTM).
 
Also, it's interesting to find that there is no software check on a 
wife with no dates, who married a man with birth/death dates back in 
the 1600-1700s. The husband can show as "not living", but if there's 
no marriage date, then the wife shows as living. Again, I'm correcting 
all these one-by-one.
 
One additional small thing I miss in FTM is the ease with which they 
had an alert on possible duplicates. I don't find that Legacy catches 
duplicates very easily. Maybe these things will change in the new version.
 
Carol





Get trade secrets for amazing burgers. Watch "Cooking with Tyler 
Florence" on AOL Food 
.


Legacy User Group guidelines:
   http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages:
   http://www.mail-archive.com/legacyusergroup@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: 
  http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

Online technical support: http://www.LegacyFamilyTree.com/Help.asp
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp

RE: [LegacyUG] Help with Living/Non-Living

[ronald ferguson]

Carol,

Please make life a little easy for yourself unless you really, really enjoy 
clicking your mouse :-) ;

Try going to Tools>Set Living these two clicks plus one that says "Go" will 
auto-set *all* those who should not be living as deceased. By "all" I mean 
those who have no birth and/or death dates as well, provided that there is some 
other information that enables Legacy to work out that they are past it eg a 
g.g.g.g.grandson. 

Ron Ferguson

_

New Blog: Free Contacts Database for use with Open Office
http://www.fergys.co.uk
View the Grimshaw Family Tree at:
http://www.fergys.co.uk/Grimshaw/
For The Fergusons of N.W. England See:
http://myweb.tiscali.co.uk/fergys/
_







From: [EMAIL PROTECTED]
Date: Sun, 1 Jun 2008 17:37:43 -0400
Subject: [LegacyUG] Help with Living/Non-Living
To: LegacyUserGroup@legacyfamilytree.com



Many times, a research document may show the names of children, but not give 
the birth/death dates. I had 65,000 names when I transferred by database from 
FTM to Legacy. Now, on Legacy,I find this wonderful little button that allows 
me to show whether the person is living or dead.



I'm finding in my transferred data that "non-dated" children of parents who m. 
back in the 1700s, are showing as "living". Several questions: Do I need to go 
back and change each one using the Legacy button to show "not living"? In the 
future, should I just record "yes" in the death date area if I know the person 
has died, but have no dates? (I could not do this on FTM).



Also, it's interesting to find that there is no software check on a wife with 
no dates, who married a man with birth/death dates back in the 1600-1700s. The 
husband can show as "not living", but if there's no marriage date, then the 
wife shows as living. Again, I'm correcting all these one-by-one.



One additional small thing I miss in FTM is the ease with which they had an 
alert on possible duplicates. I don't find that Legacy catches duplicates very 
easily. Maybe these things will change in the new version.



Carol






_

http://clk.atdmt.com/UKM/go/msnnkmgl001002ukm/direct/01/


Legacy User Group guidelines:
   http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages:
   http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/
Online technical support: http://www.LegacyFamilyTree.com/Help.asp
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp

Re: [LegacyUG] Help with Living/Non-Living

[Robert Carneal USA]

Carol-

You said:
One additional small thing I miss in FTM is the ease with which they had 
an alert on possible duplicates.


Well, Legacy does find duplicates for you.
1. Open Legacy
2. Click on Tools (at the top)
3. one of the options is "Merge."  Click it.
4. 3 options, and you want the "Find Duplicates."

You can intellimurder your ancestors!  Go to:
1. Options >> Options >> Data Entry.
2. Look for the "Presumed Dead" section.

I have mine set to ask me if a person is living if after 90 years of 
age. If the person is older than 112, Legacy lists them as dead 
automatically. But you can choose whatever values you want.


Will that do it?

Let us know.

Robert


[EMAIL PROTECTED] wrote:
Many times, a research document may show the names of children, but 
not give the birth/death dates. I had 65,000 names when I transferred 
by database from FTM to Legacy. Now, on Legacy,I find this wonderful 
little button that allows me to show whether the person is living or 
dead.
 
I'm finding in my transferred data that "non-dated" children of 
parents who m. back in the 1700s, are showing as "living". Several 
questions: Do I need to go back and change each one using the Legacy 
button to show "not living"? In the future, should I just record "yes" 
in the death date area if I know the person has died, but have no 
dates? (I could not do this on FTM).
 
Also, it's interesting to find that there is no software check on a 
wife with no dates, who married a man with birth/death dates back in 
the 1600-1700s. The husband can show as "not living", but if there's 
no marriage date, then the wife shows as living. Again, I'm correcting 
all these one-by-one.
 
One additional small thing I miss in FTM is the ease with which they 
had an alert on possible duplicates. I don't find that Legacy catches 
duplicates very easily. Maybe these things will change in the new version.
 
Carol





Get trade secrets for amazing burgers. Watch "Cooking with Tyler 
Florence" on AOL Food 
.


Legacy User Group guidelines:
   http://www.LegacyFamilyTree.com/Etiquette.asp
Archived messages:
   http://www.mail-archive.com/legacyusergroup@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: 
  http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/

Online technical support: http://www.LegacyFamilyTree.com/Help.asp
To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp