Top 5 Uses for the Free Family Tree Analyzer

Family Tree Analyzer (FTA) is a free and powerful program from Alexander Bisset (see ftanalyzer.com). FTA has so many features that I've written about individual uses for the program many, many times. If you haven't tried it yet, here's a taste of the top 5 ways FTA can improve your family tree.

Family Tree Analyzer has unlimited abilities, and it's free.

1. Finding accidental duplicates

Your family tree may have hit a software glitch. You may have clicked the wrong fact type in a menu. Or you may have gotten a little loopy during a late-night genealogy session. No matter what the cause, FTA can find all your accidental duplicates. To create your list, read "Let Family Tree Analyzer Find Your Duplicates Duplicates."

2. Finding missing source citations

Source citations help you as much as they help someone else viewing your family tree. How can you be sure of a fact when you can't remember where you found it? FTA can give you a list of all the unsourced facts in your family tree. You can create a list that ignores certain facts you don't want to source. For instance, I don't add a source for someone's sex.

Now that I've finished an all-consuming genealogy project*, I'm working on my missing citations. To find out how to do this, read "Catch and Fix Your Missing Source Citations."

* I finished my 6th (and possibly last) complete index of every available vital record for my ancestral Italian hometowns. They're free to download at www.forthecousins.com.

3. Finding inconsistencies in your family tree

No matter how long you've been at it, there will be inconsistencies in your family tree. Unless you're working at it day in and day out, you're bound to forget how you recorded a certain type of fact in the past.

I've always been an advocate for consistency. To me, consistency is a sign of good quality control. That's why I investigated some oddities FTA found when it opened my GEDCOM file. You can simply scroll down the Main Lists/Individuals table to spot wording that stands out. Sort by different columns and scroll on through. To find out what to look for, read "It's Time to Make Your Family Tree Clear and Consistent."

4. Finding all kinds of errors

No one wants their work to be messy, but it happens. If you'd like to find and fix your errors, here's a deeper dive for you. Take a look at all you can do by reading "One Report, Endless Possibilities for Improving Your Family Tree."

5. Finding missing details you need to research

Have you ever discovered a new treasure trove of genealogy documents? Nothing could be more exciting! Sometimes we add people and facts so fast that we overlook our mistakes. That's why we need FTA as our safety net. Find out how to use the program to point out all those missing facts by reading "How to Plug the Holes in Your Family Tree."

No matter where you are in your genealogy journey, FTA offers so many ways to improve the value of your family tree. It needs to be in your genealogy toolbox.

5 Tips to Use When Genealogy Documents Disagree

I don't worry too much when two documents' facts disagree with one another. That's because I can apply these 5 tips to overcome the discrepancies. And so can you!

When genealogy documents disagree, these 5 tips help you figure out what's wrong and what belongs in your family tree.

1. Gather as Many Documents as Possible

Imagine you're piecing together a family from their town's vital records. You notice the husband seems an awful lot older than his wife when one of their kids was born. How can you find out if his stated age is reliable? The answer is more documents.

Search for all the children and check his stated age on their birth records. If only one record has the unlikely age, then that record is in error.

For an in-depth example, read "When Documents Disagree, Get More Documents."

2. Trust Earlier Documents More

I spend most of my research time in the 1800s. People back then didn't have to fill out forms all the time like we do today. Many of them couldn't even write their own name. So it's completely understandable that they may not have known their birth date.

If a woman gets 10 years younger when her fifth child is born, it's because no one knows her age. The town clerk writing the birth record asked the husband how old his wife is. Do you think he really knows?

He's far more likely to know his wife's age when their first child is born. By the time the last child is born, he hasn't got a clue. That's why it's safer to believe the earliest document to mention her age.

3. Expect Some Human Error

Italian marriages in the mid-1800s generated a lot of documents. These include rewritten copies of the bride and groom's birth records. But sometimes they're the wrong record. It's most likely a human error on the part of the town clerk.

In nine errors out of 10, the clerk included the birth record of an older sibling with the same name who died as a baby. Last week I found an 1840 marriage that included a birth record for the wrong man entirely. He had the right name, but he came from a different family!

You can imagine how the clerk's error could mess up a lot of people's family trees. That's why you need to document the bride and groom's entire families. You'll know the baby born on such-and-such a date died a year later. Then you can assume it's the next child with the same name who's getting married.

To learn how to use Italian marriage documents, read "The Italian Genealogy Goldmine: 'Wedding Packets'."

4. Understand Name Usage and Evolution

It's not uncommon for a person to use their middle name rather than their first name. It's also not uncommon for the spelling of a last name to change over time.

I've seen countless babies born with multiple names who go by only one of those names. Maria Teresa uses the name Teresa. Nicola Antonio goes by Antonio. You must stay open to these possibilities. Don't rule out a document because you know he was born Nicola Antonio and this record says Antonio. Look at the big picture. What other facts can help you confirm that Antonio is really Nicola Antonio?

The spelling of a last name can evolve or change completely. My grandmother and her siblings had the last name Sarracino. Somehow the whole family lost an R and became Saracino by 1940. Some names lose their prefix over time. For instance, the name diRuccia became Ruccia. And it's common for people to make their name less ethnic in their adopted country. (It didn't happen at Ellis Island!)

When you see a last name change, look at the first names and ages. Are they the same as the family with a somewhat different last name? That's a handy tip when you find a bad transcription or a last name written incorrectly on a document.

5. Know Which Documents Are More Reliable

Because I spend countless hours viewing vital records, I've noticed trends. Many of my ancestral hometowns provide access to death records from 1931–1942. I've found that the deceased's age on these records is highly reliable. I'll bet that that during this time a clerk verified the person's age instead of taking somebody's word for it.

I've also found that a bride and groom's age on their marriage document is quite reliable. That comes in handy if you don't have access to their birth records. The reasons for this improved accuracy may be:

• They're still young enough not to have forgotten how old they are.
• Even if we don't see the documents, the town checked their birth records before performing the marriage.

In more recent times, I've seen a variety of names applied to myself. After 2 marriages, I've had 3 last names, and they're all misspelled constantly. I get mail with 2 different middle initials, and I have no middle name! Then there's my first name with its made-up spelling. My entire name is rarely spelled the right way.

If a genealogist is trying to research me in the distant future, good luck to them! It's going to take a whole lot of documents to make sense of my name alone.

Put these 5 tips to use and keep them in mind when you're researching your family tree.

How to Overcome a Town Clerk's Errors

Some of the mistakes I'm seeing on vital records are shocking. No one's perfect, of course. But you'd like to think the clerk recording a birth record got the facts right.

As I work my way through the vital records from Grandpa's hometown, I'm uncovering lots of errors. The errors fall into a few main categories:

• Wrong date. Sometimes you'll see a February 30th slip in there. Other times the date of birth is a day after the date they wrote the document. Not possible.
• Wrong first name of parent. People with multiple names may go by any one of them. A Giuseppe Nicola Bianco may call himself either Giuseppe or Nicola. I have to keep that in mind when I try to find this person in my tree. But I've seen my ancestor Saverio called Francesco when Francesco was never part of his name.
• Wrong last name of mother. I've had trouble placing a baby in my tree when their mother's last name is wrong on the birth record. I try to verify the right name with the child's death record or the births of their siblings.
• Wrong ages for parents. This is far too common and not the clerk's fault. Before you had to state your birth date regularly, people didn't know exactly how old they were. They're generally in the right ballpark, but sometimes they're way off.
• Wrong last name for baby. This has tripped me up a few times. Somehow the parents' names are correct on the birth record, but the baby's last name is an error.
• Spelling variations. I know my ancestral hometowns, so I know the typical spelling variations to watch out for. Iamarino becomes Marino. Iavasile becomes Basile. Iazeolla becomes Zeolla. These names are sometimes interchangeable.

We want to take vital records as gospel, but human error will always find a way in. Here's how to handle these errors in your genealogy research.

How to Know What's Correct

As I've mentioned so many times that you're sick of reading about it, I'm working my way through ALL the vital records for Grandpa's hometown. At least 95% of the people can fit into my family tree somehow. As I build out every single family, these errors become plain to see.

The other day I began going through the 1854 birth records. I found one baby, and when I finally located her parents (there was a name error), I saw my note. It seems I'd already found this baby's death record and entered that date. But I couldn't find the baby's birth record (because of the name error). For a birth fact, I had a calculated year based on the age at death, and one of my standard notes in the description field. "Birth record not found."

Now I know why I couldn't find the birth record. The document had an error. But by process of elimination, I know know that the birth record with the error can only belong to this person.

How to Record the Errors

I've made a habit of adding a standard line of text to explain the error. I put this text in the description field of the fact with the error. For example:

• If a birth record has the wrong last name for the baby's mother, I enter: His mother's last name is Marino on his birth record.
• If a death record uses a different first name for a person, I enter: She is called Mariangela on her death record.

If documents provide competing facts, I add a bookmark to the person and a more detailed note. For example, Italian marriage records can include the death record of the groom's grandfather. Many times I've found that it's the wrong record. Right name, wrong guy. But sometimes it's a different date, and it isn't clearly another guy. This calls for a note.

With a broader knowledge of your ancestor's town, you can see past the human error in vital records.

Rules to Keep in Mind

If you get familiar with the people of your ancestral hometown, a lot of things will become clear to you.

• People didn't always go by their given name.
• People didn't know how old they were.
• People's names can get really messed up.
• If a person died in another town, that town's clerk may have no idea who the deceased's family members are. Or how old they are. It's not like they were carrying a driver's license or had an In Case of Emergency contact on their cellphone.

If you're familiar with the last names in town, you'll be ready to search for a Basile when you can't find a Iavasile. And if you know how the vital records work, you won't rely on a person's stated age unless you see:

• their birth record, or
• their marriage record for which they had to supply their birth record.

Human errors can be so frustrating to your genealogy research. I know I feel better about my choices when I leave a note to point out the discrepancy. If new evidence comes up and proves I made a wrong choice, it's good to see that note and understand how it came to be.

In fact, this falls more into my own human error, but I want to share it. For my ancestral hometowns, the marriage records end in 1860. After that, the clerk usually wrote a marriage notation in the column of the birth record. As I enter a baby into my family tree, I add their future spouse's name and their marriage date. In the description field I enter either, "From her birth record" or "From his birth record." When I find the right spouse's birth record, I change the description to "From both their birth records." That's a nice confirmation when there is no marriage record.

The other day I found that I'd made a wrong assumption about a groom. When I found the right groom, with the same exact name, I had a dilemma. But then I saw my note. For the wrong groom's marriage fact, it said only "From her birth record." Now that I'd found the groom with the matching marriage notation, I knew for certain that the other guy was wrong. I detached him from the bride and her kids.

Remember that mistakes happened a lot. Examine as many records from the town as possible to get a feel for the names and make these errors stand out. And develop your own standard language to let future you know why you did what you did.

An End-of-Year Tune Up for Your Family Tree

The end of the year is a perfect time to give your family tree a thorough check for errors. How many times during the past year did you:

• Add a person without checking if their birth date fits in with their parents and siblings?
• Change the way you record a particular fact, like someone's nickname?
• Accidentally attach a marriage date to the first spouse instead of the second?
• Update a person's birth year without changing their parents' estimated birth years?
• Attach a census fact to the youngest child in the family who wasn't born yet?

All kinds of human errors can happen while you're caught up in the genealogy zone. I generated two reports to find errors in my more than 33,000-person family tree:

• In Family Tree Maker, I ran the Data Errors Report.
• In Family Tree Analyzer, I opened a brand new GEDCOM file to look for the usual types of errors. If you don't use Family Tree Maker, create or download a GEDCOM file of your family tree. Then open it in Family Tree Analyzer and check out the error list.

Human error will always creep into your genealogy research. Here are 2 reports that will find the mistakes in your family tree.

I saved the Family Tree Maker report as a very long PDF file. It's long because it lists "The marriage date is missing" each time I don't know a couple's marriage date. That isn't an error. These early documents aren't available, so I'm ignoring that message.

The report also thinks it's an error when a husband and wife have the same last name. It isn't. I use only maiden names for the women in my family tree, but sometimes a Marino marries a Marino. What're you gonna do?

Here are the errors from the Family Tree Maker Data Errors Report that I'm fixing in my family tree:

• The birth date occurred before his/her father/mother was 13. This happens when new information changes my estimated birth date for a person. Let's say I add a person to my family tree with a birth year of 1800. If I know their parents' names, I give them an estimated birth year. My rule is to say the parents are 25 years older than their oldest child—until I find hard facts. So I'll give the 1800 baby's parents an estimated birth year of "Abt. 1775." But what if I discover that baby was born in 1782? If I don't redo the math for the parents' estimated birth year, I'll have a "parent too young" error.
• The birth date occurred after his/her mother was 60. I have two very large families where the children's births spanned way too many years. In one case, the oldest child was so much older than the rest that their birth year had to be wrong. I had to look at their children, too, to make sure I used a valid date estimate.
• The birth date occurred more than one year after his/her father died. This happened with people born in the 1700s. All I could do was adjust the child's birth year to the year their father died.
• The birth date occurred more than one year after his/her mother died. Same problem as above.
• Baptism date occurred before individual's birth date. This was my typo, and I' glad the report pointed it out.
• The individual was married before the age of 13. Unfortunately I have a couple of cases where that's true.
• The marriage occurred after the death date. A man's wife died before him, and I marked his death date as After her date. Then he remarried, and I forgot to delete that death estimate.

These reports will find conflicting facts in your family tree.

• The marriage occurred after the spouse's death. I must have given a marriage date to the first spouse instead of the second. It's too easy to make that mistake.
• Event immigration (or divorce or marriage) contains no data. I can't explain how some of these happened, so I appreciate this safety net.
• This individual's children sort order may be incorrect. I thought that was automatic. I may have clicked the wrong button on this family.
• Person does not have a preferred spouse set. Somehow I added marriage date without adding a spouse's name.
• The birth date is missing. These are living people I added recently. I don't know how old they are, so I'll have to add estimates based on their parents' ages.
• The name may include a nickname. I had a man's nickname in parentheses with his name. Now I've changed the nickname to an alternate Name fact.
• Residence date occurred before individual's birth date. The 1940 census says where the family lived in 1935. It may be the same house or the same place/town. Twice I gave the 1935 address to kids born after 1935. Now I've deleted those residence facts.
• The age at death is greater than 120. This is usually not an error. If I don't have a document to tell me when someone died, but I know they were dead when their child died, I'll say they died "Bef. [the child's death date]." This error report isn't taking the "Before" into account.
• The burial date occurred before his/her death. This was my typo, but yikes! What a thought.

Find those troublesome families in your family tree with one of these genealogy error reports.

When you're working in Family Tree Maker, the software will make an alert sound if:

• You add a baby to a parent who's too young, too old, or too dead.
• A bride or groom is under the age of 13.
• A husband and wife have the same last name.

I appreciate those warnings—except for the last one. But if you update someone's birth date later, you may not get the warning. That's what these reports are good for.

Give your family tree an error cleanse before the new year. Start off 2022 with a cleaned-up, fine-tuned, fortified family tree.

2 Ways to Give Your Family Tree a Checkup

Don't wait for an annual checkup for your family tree. Do it often.

Have you added any people to your family tree lately? Have you added or changed any facts? Then it's time for a checkup.

Even when you think you're being extra careful, mistakes can happen. Why not spend a few minutes every 2 months or so to find and fix your slip-ups? The things you forgot and the goofs you made will surprise you.

Here are 2 ways to give your family tree a checkup. You'll feel more confident about your tree after you've fixed some errors. You'll feel even more confident if you don't find any errors!

1. Run Family Tree Analyzer

The free Family Tree Analyzer program gives you one-stop shopping for all kinds of errors. Launch it, load your latest GEDCOM file, and click the Data Errors tab.

Check all the boxes to find these errors:

• Birth dates that are:
  
  • after the person's death
  • more than 9 months after their father died, or any time after their mother died
  • before either of their parents were 13 years old
  • after their mother turned 60 years old
• Death dates that are:
  
  • after their burial (yikes)
  • after they were 110 years old or more
• Marriage dates that are:
  
  • after the bride or groom's death
  • before the bride or groom turned 13 years old

Give your family tree a quick checkup with the powerful error finder in Family Tree Analyzer.

You may have what I call legitimate errors. For instance, I do have some babies who were born before one of their parents was 13. In one case, when I looked in my family tree, I found a note saying "The mother was 12 years old." That's more of an "unlikely" than an "impossible" feat.

I also have a baby born almost 11 months after his father died. But that's what the birth record says. I have a note wondering about the man who reported the baby's birth. Is it possible he was the real father?

If seeing all the errors at once is too much, click one checkbox at a time, and resolve or look into those errors.

2. Check Your Family Tree Software

The only family tree software I've ever used is Family Tree Maker. I hope that you're using desktop software for your family tree, and not keeping it only online. Building your tree online doesn't give you the same level of control. And you'll miss out on lots of features.

Every once in a while I check a few of the tabs in Family Tree Maker for errors. This time around I found several place-name errors. I'll bet they got messed up when I had a failed synchronization with Ancestry.com. But they were an easy fix.

In Family Tree Maker, look at these tabs:

• Check Media for images that are:
  
  • uncategorized
  • missing a caption, date, or other information
• Check Places to find any that are not properly categorized
• Check Sources to find any that have no facts associated with them

Each tab in Family Tree Maker gives you a different way to find errors.

If you give your tree regular checkups, your errors should be minor. Of course, your first checkup may be a bit of a shocker.

Make this a routine and keep your family tree healthy and hearty.

4 Types of Family Tree Errors Only You Can Find

Place names are a big challenge in your family tree. Can you improve yours?

I'm working on a new family tree project that I hope to share with you soon. My goal is to create visualizations of my family tree like you've never seen before.

I'm preparing the data for this project, going through long spreadsheets almost one line at a time.

But I discovered something along the way. In fact, I discovered lots of things: errors that no software tool can find for me. They're human errors that are obvious only to the human that made the errors. Me!

What I had was a very long list of every address or state or country in my family tree, and each name associated with it. As I scrolled through the list, I saw my mistakes: I had people associated with places I know they've never been.

It's easy to click the wrong suggested place. Time to find those errors.

1st Error Type: Wrong Selection

Family Tree Maker is great about suggesting place names as you type. Each time I start to type "Italy" I see the next suggestion is a place called Italy Cross in Canada. And I did it. I accidentally associated two 18th century Italians with Italy Cross, Canada by mistake. I made a similar mistake with a couple that lives in Argentina. Who even knew there was a place called Argentina, Alajuela, Costa Rica?

2nd Error Type: What Was I Thinking?

I had another man from Pennsylvania associated with Hamilton, Bermuda. It's marked as a departure, citing the New York Passenger Lists as a source. But there's no date, no image, and no travel companion. It seems like a complete mistake. And since this man is the father of an ex-in-law, I'm deleting the whole fact.

3rd Error Type: Inconsistency

I also spotted a style error. My standard for U.S. addresses is to spell out the word County. For example: 328 Superior Street, Youngstown, Mahoning County, Ohio, USA. In the long list of places in my family tree, I saw a couple scroll by that were missing the word County. It may not be a big deal, but I'd rather have it be right.

4th Error Type: Stragglers

While looking for an example of a place name missing the word County, I found another type of error. An address belonging to no one. It probably belonged to someone who used to be in my tree. But I've decided to limit the scope of some far-flung branches. Because I deleted a lot of people, I may have a bunch of straggling place names like 17 Halls Heights Avenue.

The people are gone, but their addresses linger on.

To find these types of errors in your family tree, you can start by browsing the list of places you've used. Family Tree Maker has a Places tab. RootsMagic has a Place List. I don't use FamilySearch, but I don't see a lot of control options there.

Do any places stand out as being odd to you? I ran the Family Tree Maker Place Usage Report to generate a list, but it doesn't include places that have no people associated with them.

Add this task to your Rainy Day Genealogy List or your I'm Bored Genealogy List. It's another effort that'll make your family tree that much stronger.

And speaking of fact-checking:

• How to Spot and Fix a Big Mistake in Your Family Tree
• How Is That Possible?
• Case Study On 'How Is That Possible?'

It's Time to Make Your Family Tree Clear and Consistent

How can you find and fix genealogy inconsistencies? And which style should you choose? Read on.

Have you always recorded facts in your family tree in the same way? Or did you do it one way when you first started, and figure out a better way later?

Being consistent is important to the long-term future of your precious genealogy research. If you leave behind an inconsistent family tree, your work will cause more questions than answers.

It can be hard to stick to a format when you can't work on your tree that often. Make some style decisions now, and you can continue creating your lasting legacy.

Three Examples of Choosing Consistency

1. Fact Types

Recording a deceased relative's Social Security Number can be helpful. Say you find a document for a person with the same name, but a different SSN. That number can prove a document does or doesn't belong to your relative.

I wasn't consistent when I started this hobby. Sometimes I used the SOCIAL SECURITY NUMBER fact in Family Tree Maker, and sometimes I used the SSN ISSUED fact. But the SOCIAL SECURITY NUMBER fact makes more sense. You can record the number as well as the date and place where it was issued.

Yesterday, I:

• located each SSN ISSUED fact in my tree
• added the date and place to the SOCIAL SECURITY NUMBER fact
• deleted the SSN ISSUED fact.

2. Immigration Details

The first records I collected for my family tree were ship manifests. Nearly every one of my ancestors passed through Ellis Island. Recording all these immigration facts is very important to my family history.

At first I used only the IMMIGRATION fact type, recording the date and place of arrival with a note about the ship name. Then I realized I could record the date they left Italy, too. That's written on the manifest.

But I had to make another choice. I can choose ARRIVAL, DEPARTURE, EMIGRATION and IMMIGRATION as fact types. Which should I use? A more experienced friend suggested I use EMIGRATION and IMMIGRATION for a person's first trip to their new country. I'd save DEPARTURE and ARRIVAL for:

• Pleasure trips, like a honeymoon or vacation, or
• Return trips, like visiting the old country to see your parents or bring back the rest of your family.

I made my choice and updated my fact types. I added in the missing emigrations or departures, too.

3. Names, Dates and Places

If you're using a decent family tree program, you can select how you want to display these types of facts.

Your family tree software should give you the option to choose how to present your data.

People's Names

Some genealogists choose to display everyone's last name in all capital letters. I don't want to do that because I have many names that begin with a small letter, like deBellis. I don't want to lose sight of that.

Some people choose to display a woman's married name rather than her maiden name. I don't want to do that because:

• my female Italian ancestors kept their maiden name for life, and
• which name do you use for a woman who married more than once? The last name that relates to you, or the final husband's name, even if he's nothing to you?

Dates

Working for an international company made me aware of writing simply and clearly. Avoid local phrases and use international dates. In the United States we're used to the Month/Day/Year format (12/28/2018). But some countries use the Day/Month/Year format (28/12/2018). Others prefer Year/Month/Day (2018/12/28).

Think of how many dates can be misunderstood by someone in another country. Is 5/4/2019 May 4th or April 5th? It depends on where you live.

To avoid confusion in my family tree, I use DD Mon YYYY, as in 28 Dec 2018. Any English-language speaker will understand this, and many Romance-language speakers will understand it, too. Their month names aren't so different from ours.

Places

For a long time I wouldn't let Family Tree Maker "resolve" addresses or place names for me. For one thing, I thought it was silly to put "USA" at the end of a New York City address. Where else do you think New York City is?

As time went by and my tree's international members outnumbered the Americans, I decided adding "USA" wasn't a bad idea.

But one difference I've stuck to is county names. Leaving out the word "County" can lead to confusion. What if you have only the name of the county someone lived in, and not the town? Will that be clear? So rather than Beaver, Pennsylvania, USA, I'll enter Beaver County, Pennsylvania, USA.

Whatever you decide to do, make sure it's easy for anyone to understand, and stay consistent.

Finding and Fixing Your Inconsistencies

What brought this to my attention was a free program I've written about several times: Family Tree Analyzer. (Now available for Mac users.) When I ran the program and opened my family tree's GEDCOM file, I saw a few things on the main screen that I didn't like:

• Found 14 facts of unknown fact type SSN ISSUED
• Found 13 facts of unknown fact type OTHER
• Found 1 facts of unknown fact type RELEASED

This free program will uncover inconsistencies in your family tree.

I wanted to find these facts and change them. I discovered an option in Family Tree Maker to Manage Facts from the Edit menu. I chose a fact type, clicked Data Options and saw a list of every person using that fact type. I visited each of these people in my tree and made adjustments.

The fact type OTHER turned out to be something I did because I didn't know how to characterize these facts. Each person using OTHER had been in the Japanese-American prison camps of World War II. These particular facts were the dates they were incarcerated and released. I changed each of these entries to use my custom fact type, Internment.

One man named Luigi was using the RELEASED fact type. This was the date they released him from quarantine on Ellis Island. Because it was a medical quarantine, I switched to the MEDICAL CONDITION fact type.

For other types of changes, you may be able to use Find and Replace within your family tree software. Be careful. Before you click OK to make a global change, think about what else might change.

If you're changing a county name, is there a person with that name? Will their name change from John Sullivan to John Sullivan County?

Running Family Tree Analyzer showed me a Find and Replace blunder I'd made. I messed up some Italian last names that are the same as Italian occupations. Everyone named Canonico became "canonico (member of the clergy)". Oh boy. I fixed this with some careful one-at-a-time finding and replacing.

Even if you're not thinking of your genealogy hobby as your legacy, think about your own sanity. If you don't work on your tree for a while, how many of these inconsistencies will make you say, "What was I thinking?"

And speaking of Family Tree Analyzer:

• Run This Genealogy Report To Help Clean Up Your Dates
• How to Find Errors in Your Family Tree
• One Report, Endless Possibilities for Improving Your Family Tree

3 Tricks for Better Genealogy Search Results

When your family won't turn up, try some tricky searches.

How many times have you searched for your relative in a set of documents and found nothing? Or maybe you found a ton of results that looked like junk to you.

There's a good chance that the search results are bad because the transcription was bad. Did the volunteer transcriber have trouble reading the bad handwriting? Did they enter dramatically wrong data into the system?

Your search is doomed to fail, right? Not necessarily.

If you use partial searches, related searches and detailed searches, you may find your family.

1. Partial searches

It was common for our ancestors to have a first name and a middle name. But how were they identified on the census form? Did the person providing the information know them by their middle name only? Or by an adopted name in their new country?

Try leaving their first name out of your search completely. Fill in their age and place of birth, but use only their last name.

Try the opposite, too. I had more luck finding my grandfather on a census with only his first name of Adam. The census-taker wrote his last name in a way I hadn't expected.

Simplify your search. Toss out the extras, and your results may improve.

2. Related searches

When a family is tough to find, look at the kids. The particular combination of children's names in this family can be the key to finding them.

Do a search that includes all the kids' names. Leave off the last name and let the search focus on finding those kids together.

You can also try using the husband and wife's first names only. That combination may be what does the job.

3. Detailed searches

I'm having trouble finding my great grandfather's naturalization papers. His name often causes me problems. His given name was Pasquale Iamarino, but on some documents he is Patsy Marino. Or a combination of those names.

So I searched using his exact birth date. I didn't find him. I also searched using his birth year and town of birth, but no name.

His naturalization isn't showing up yet. But, I once found his wife's brothers on ship manifests by searching for their last name and town of birth only.

Here's an example using Pasquale Iamarino. I did a general search of all categories on Ancestry.com. I entered only his last name, his town of origin and his exact year of birth.

The results were terrific. In fact, they include one new result that I never expected to find. It's the claim ID for his railroad retirement pension. I'll have to buy a copy of it from the National Archives at Atlanta (why there?), but this is brand new information.

So many misspellings, but the results are all for my great grandfather.

My dad says Pasquale may have had black lung disease from years of cleaning out the furnace of coal-burning train engines. He had to retire early on disability. This pension claim may tell me a lot more about what happened to him.

Also, the Suggested Records in the right column of my Ancestry.com results are very impressive! Despite all the spelling variations, that exact birth year seems to have done wonders for my search. All those records belong to my great grandfather.

The point is to experiment. Don't give up if the results don't look promising. All these genealogical records are a gigantic database. You may need to slice and dice that database to get past bad transcriptions and misspellings.

Give it a try the very next time you don't get the results you want. Do a partial search, add in related names, or toss out the names and plug in specific facts.

Working on your family tree is a big puzzle. Clever searches are yet another piece of the puzzle.

Don't get frustrated. Get clever.

And speaking of searching:

• Let a Few Quick Wins Reinvigorate Your Genealogy Research
• Find Those Stubborn Genealogy Documents with Creative Searches
• 3 Ways to Find Your Ancestors in a Huge Pile of Documents

How to Find Errors in Your Family Tree

Update: Family Tree Analyzer is now available for Mac.

The mission of this blog is to encourage genealogists to improve their family trees. To fortify your family tree means to:

• Use the best sources for your facts.
• Locate as many pieces of documentation as possible.
• Analyze your tree for errors and fix them.
• Add thorough, consistent, provable facts throughout your tree.

This quick report lets me see the oldest direct ancestors in my tree.

The more your tree grows, the harder it can be to find its errors. Maybe you added lots of facts when you were first building your tree and didn't add any sources. Maybe you borrowed from someone else's tree and later realized they were wrong. Or maybe you accidentally transposed the numbers in a bunch of birth years.

Family tree errors can happen to a professional genealogist as well as an excited newcomer.

How can you find the errors when your tree is big and you've been working on it for years? How do you find a handful of needles in a haystack?

Reporting Software

Reporting tools can point out all kinds of family tree errors, showing you exactly where to jump in and start fixing.

I've written about the free software tool called Family Tree Analyzer (FTA) twice this year. (See Why You Should Be Using the Free "Family Tree Analyzer" and Run This Genealogy Report To Help Clean Up Your Dates to download the software and see what it's about.)

Get the latest version from the source: http://ftanalyzer.com. Go to the Software.Informer website for free GEDCOM analyzers that work on Mac or Windows.

I knew I'd barely scratched the surface of what FTA can do. Now I'm using it to identify a variety of errors I can fix in my family tree.

The first step is to run your family tree software and export a standard GEDCOM file. This is the agreed-upon standard that makes your family research transportable and sharable.

Then run FTA and import your GEDCOM. The first thing you'll see is a long summary of the types of facts found in your tree. My favorite part is this list:

• Direct Ancestors: 189
• Blood Relations: 1,451
• Married to Blood or Direct Relation: 541
• Related by Marriage: 12,452

Click the Data Errors tab. You might see a long list of errors. Some are more important than others, so click the Clear All button. Now click to select one type of error, such as Birth before father aged 13.

My tree has nearly 20,000 people, and I discovered the majority of them in old Italian vital records. Some of the documents had errors. Others had conflicting information. In tons of cases, I had no age or birth year for parents, so I chose to make them 25 years older than their oldest child.

For Maria Giuseppa Verzino, shown in this error report, I have evidence that she was born in 1799. But her father Paolo has a birth year of "About 1791".

Error report for seriously under-aged fathers.

I try to be very consistent in my family tree. Whenever I see "About" for someone's birth year, I know that I subtracted 25 from the birth year of the person's oldest child. But maybe I found more of their children later. Maybe when I found Maria Giuseppa and her birth year of 1799, I forgot to update her parents' birth years. Maria Giuseppa probably has a sibling born in 1816. When I recorded that sibling, I subtracted 25 from 1816 and marked the parents as being born "About 1791".

This is easy for me to fix. I can go to Paolo Verzino in my tree and see if I've found any children born before Maria Giuseppa in 1799. If not, Paolo and his wife's birth years should be updated to "About 1774".

That's one less needle in the haystack of errors.

Now uncheck that error and select another one, like Marriage after death. I have one of these errors. My family tree says that Giuseppe Antonio delGrosso was married on 11 December 1859. But I have his death recorded as "Before Dec 1859". That needs to be looked at.

Work Through the Errors

You can work your way through the errors and correct them one by one.

FTA contains a lot of tabs and menus. Click them to see what may be useful to you. The Facts tab can show all of your direct-line ancestors in a list. Choose only Direct Ancestors in the Relationship Types section. Then choose any fact, such as Birth. Click Show only the selected Facts for Individuals.

The resulting table shows me at a glance that I've identified two sets of my 9th great grandparents born in the early 1600s! I can click any column to sort by relationship, last name, date of birth, etc.

That isn't an error to fix, but it is a way to double-check my ancestor chart where I'm keeping a list of all direct-line ancestors. (See How to Visualize Your Ancestor-Finding Progress.)

So take a break from finding new ancestors, and make the time to fix the errors in your family tree. After you've fixed a bunch of them, export a new GEDCOM. Open it in Family Tree Analyzer and see how much shorter your errors lists are.

Fixing errors is every bit as important as finding that missing census file or death record.

Find out what else you can do with this free software:

• Use This Tool to Discover Family Tree Insights
• Why You Should Be Using the Free "Family Tree Analyzer"
• Run This Genealogy Report To Help Clean Up Your Dates
• How to Handle the Unrelated People in Your Family Tree

Case Study on "How Is That Possible?"

Here's a lesson that supports my earlier post, "How Is That Possible?" When my recent post about Italian marriage records led me to discover a mistake I had been making, I spent three solid days correcting my tons of such records in my enormous family tree.

The work was tedious, but after a while I realized that this change I was making—reclassifying certain dates as "marriage license" rather than "marriage"—provided the answer to a question that had come up a number of times.

I had quite a few men (these are small-town Italian men in the 1800s) who had gone through the process of posting their intention to marry a woman and then seemed to marry her, but went through the same process with another woman a month later.

What was going on? Divorce was not a thing, and the first wife had not died. In fact, I had proof that the first woman then went through the process with another man and married him.

Once I learned that they had not gotten married, but had merely obtained consent to marry, it became clear: The first couple intended to marry but something prevented the marriage. Each of them was then paired with someone else whom they did marry.

See When is a Marriage Not a Marriage?

I feel this corrected and more logical information makes my family tree even more solid. So I ran Family Tree Maker's built-in error report and uncovered a page full of birth date discrepancies. Some people had two birth dates from conflicting resources, while others had an original placeholder date that had been superseded by documented facts. So I was able to clean up all of the errors.

I even figured out and fixed the error I highlighted in How Is That Possible? where I had two Michele Leone's with the same birth date. The date belongs to my grandfather's first cousin; the other Michele Leone is a more distant relative born a different year.

Now I'm itching for other discrepancies to fix!

Case Study on "O Brother, Where Art Thou?"

Here's a lesson that supports my earlier post, "O Brother, Where Art Thou?" I have one branch of my family where the information was pretty scant. In fact, I never knew my great grandmother's maiden name was Caruso until the eve of my first trip to Italy—the trip that sparked my interest in genealogy. Later I heard from a distant cousin named Michael who was very interested in the Caruso family tree and shared a great deal of first-hand information with me.

As with any information I receive without documentation, I set about proving all of the facts Michael had shared with me, and in doing so, I learned quite a bit more facts.

My great grandmother, Maria Rosa Caruso, had at least four older brothers, all of whom came to upstate New York in the very early 1900s. Giuseppe came here first because each of this brothers' ship manifests says they were joining their brother Giuseppe at 827-829 Canal Street, Elmira, New York.

Maria Rosa's ship manifest was the hardest to find, and even after finding it, I was not sure it was the right Maria Rosa Caruso for quite some time. The manifest has some facts that are correct for her (born in 1880 or 1881 in Pescolamazza, and coming to join her brother Giuseppe), but it also has facts that do not work.

The manifest says she was married as of July 1906, but that doesn't work because I have her November 1906 marriage certificate from Hornell, New York. It also says her final destination is Addison, New York. While that is not terribly far from Elmira, or even Cameron, New York, which is another place her brother Giuseppe lived, I have no facts putting any members of this Caruso family in Addison. There is an address beneath her brother Giuseppe's name, but it appears to say "236 Bore". I can't make anything out of that.

I kept returning to this 1906 ship manifest and finally noticed something very important. Where the manifest shows an "m" for married, in much lighter ink there is an "s" for single overwriting the "m". (See the far-right side of the image.) So it was an error.

That left me with the troubling town of Addison. But in a web search today I discovered that Addison was the end of a particular railroad line that connected with the New York Central Railroad. So there is a good possibility that Maria Rosa had her ticket from New York City to Addison and then had to get on the Erie Railroad to get to her brother. At that time, Giuseppe lived in Cameron, New York, on a street parallel to the railroad tracks where he worked. I can see a railroad line on Bing Maps that runs from Addison to Cameron. And on her marriage certificate, Maria Rosa lists her residence as Cameron.

Now I feel as if the 1906 ship manifest finally makes sense. And this illustrates how important it is to gather as many provable facts as possible about your ancestor and their entire family.

How Is That Possible?

They say the "unexamined life is not worth living". I say the "unexamined family tree is not worth publishing"!

Check Your Facts

Occasionally you need to analyze your family tree to see if anything looks illogical. Your family tree software may alert you if you’ve entered facts that are impossible, such as a woman giving birth when she’s a little girl or after she’s dead. But it won't alert you if your facts show a person living in two different states at the same time.

See why I think Family Tree Analyzer may be perfect for you.

Don't leave impossible facts in your family tree.

A common name in my family,
but 2 with the same birth date?

Recently I was adding census data to my family tree. One set of facts said the wife came to America two years before her daughter.

If this were true, it would mean she left her infant daughter in Italy, came to join her husband in America, and didn’t send for her baby for another two years.

That's highly unlikely and can only be proved or disproved by finding the mother and daughter’s immigration records.

These types of logic errors are what I frequently find in other people’s family trees—a big reason why I never accept someone else's research without seeing the documentation. Many times, these errors are difficult to spot and difficult to solve.

I like to put a bookmark on people with a logic error so I can quickly see where more investigation is needed.

See what type of reporting features your software may have. Whatever tools you can use, your tree will benefit from a logic scrubbing.