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.

Finding and Fixing an Awkward Typo in Your Family Tree

I spent too many months fixing errors in my family tree to tolerate any more. I knew my previous lemon of a computer was the main source of the errors. Tons of duplicate source citations were born of failed syncs between Family Tree Maker and Ancestry.com. (See "Take the Time to Improve the Sources in Your Family Tree.")

Recently, I keep seeing another type of error. I'll notice a person with a male name marked as a female. I wondered if it was a typo I kept making. When I add a new name, my fingers are so fast on the keyboard that I sometimes press F for female before I realize it. I've caught myself doing it, and then I can fix it before moving on.

How many of these typos are in my huge family tree? How many men did I mark female? How many women did I mark male? How can I find them all?

Don't read anything snarky or political into this subject matter because it isn't there. There's one very important reason to make sure you've used the right gender. If you wind up with a wife labeled male, the couple's children will get her last name. Is that how names work in your culture?

The less important reason for fixing this error is you don't want to look like you don't know what you're doing. If you're recording history, you've got to strive for accuracy. I record each person by the name on their birth certificate, even if they went by another name in life. So I'm going to record their sex, too.

Looking for an Easy Way to Spot the Error

Since I use Family Tree Maker to build my tree, I wondered if a filter might help. I created a filter of all people in the tree with a sex of female. That cut my 66,000-person family tree list of names about in half. But that's too many names to scroll through and spot the out-of-place names.

I thought of Family Tree Analyzer because I knew I could sort the data like a spreadsheet. I opened my latest GEDCOM file and went to the Main Lists / Individuals tab. I sorted the Forenames column from A to Z (an important first step). Then I filtered the Sex column to display only F for female.

Is this type of error hiding in your family tree?

If you only keep your family tree online and do your work there, download a GEDCOM from the website. Open the file on your computer with Family Tree Analyzer, and make all the corrections one by one.

My list was still long, of course, but it didn't take too long to scan. With the first names in alphabetical order, I could scroll quickly past everyone named Maria, for instance. I acted on 4 types of first names:

1. Clearly male names. If you have lots of names based in another language, understand the rules of that language. Most of my Italian first names ending in the letter a will be female, but there are exceptions. Nicola, Mattia, Andrea, Giambattista, Zaccaria, etc.
2. Possibly male names. Among my Italian ancestors, the first name Felice could belong to either a male or a female. In English, think of a name like Dana.
3. Typos that stood out in the alphabetical list. I saw Antona instead of Antonia.
4. A last name as a first name. A name like Viola may be a first name, but in my tree it's also a last name. I need to see this person's full name. Italian names are often written last-name-first on vital records, so I may have absentmindedly entered a name backwards.

Of all the females, there were 92 I needed to review in my family tree and a much smaller number to change to male. When I finished, I changed my filter in Family Tree Analyzer to display only people with an M in the sex column. I scanned the long list for any female names, questionable names, or typos. I didn't count them, but there were at least 10 I changed to male.

If you're working on your family tree, a wrong-sex error is very visible when you find one. The person's name may be in a field of pink instead of blue, or they're on the left side when you expected them to be on the right.

I don't know how each of these errors happened. Now that it's top-of-mind, I'm hopeful I won't keep making the wrong choice out of muscle memory.

Pinpoint Important Places in Your Family Tree

When I used the Maps menu in Family Tree Analyzer (FTA), I discovered something I needed to fix. Even though I can find many addresses from my tree on Google Maps or Bing Maps, they weren't recognized by FTA.

I opened my tree in Family Tree Maker, which uses Bing Maps for locations. I noticed it could be very imprecise, or just plain wrong, about some locations. I wanted to improve these results so I could do more with FTA's Maps menu. The solution was to add Latitude and Longitude coordinates. And it's easy to do.

If small-town locations in your family tree are hard to find IRL, these two numbers will bring you right to the front door.

Here's how to add these precise coordinates to your computer-based family tree software:

• Find the exact location on a map website. I like Google Maps for this because of its streetside view. I want to see that I've got the right place, and even find the front door.
• Right-click at a precise location to see the map coordinates. (You must exit Street View first.)
• Enter the Latitude and Longitude numbers in your family tree.

I use Family Tree Maker, but RootsMagic also has fields on the Places menu to enter map coordinates. I'm sure other desktop genealogy programs do, too.

Family Tree Maker tells me I have 5,323 places in my family tree, so I'm not going to do this for every location. My goal is to use Family Tree Analyzer to see how many people got baptized or married in a particular church. So for starters, I'm pinpointing the locations of different churches in my family tree.

Watch Your Results Get Better

Here's an example of the benefits of this project. Before I added map coordinates to one church in Benevento, Italy, Family Tree Maker had their pin a few miles south of the city. I have no idea why. Now, with the coordinates in place, FTM knows precisely where to find this church. And so do I, should the day come when I want to visit it. As I look at the map, I see that I've been within a few yards of this church, but I didn't know it!

How many people in your family tree were at this address? Family Tree Analyzer can tell you, but you may need to feed it a couple of numbers.

With a few churches pinpointed in my family tree, I'll export a new GEDCOM file to open with Family Tree Analyzer. I'd like to see how many births and baptisms I've associated with the church in Colle Sannita, Italy.

In Family Tree Analyzer, once you open your GEDCOM file, click the Maps menu and choose Show Places. Say No to the pop-up message about Geocode locations. Now choose a particular location.

I clicked through the list of places and drilled down to the church. Italy, Campania, Benevento, Colle Sannita, Chiesa di San Giorgio Martire. There's my answer. I've attached this location to 14,724 baptism or marriage facts. And because of the map coordinates, the location is very precise.

Recently I've been reviewing some of my early research work on the town of Baselice. I was brand new to Italian vital records when I recorded many of these facts. I remember I didn't want to assume each baby got baptized in the town church. Now I know better. And I can see that the church is in fact mentioned on the birth or baptism records. I'd like to correct those baptism facts and increase the number of uses of the church in Baselice.

Make Your Map Pins Portable

I'm excited to use these map coordinates the next time I visit my ancestral hometowns. Family Tree Analyzer can export all the places from your family tree to "Google My Maps." I gave this a try, and it saves a file to your computer in a text-based format. When I go to My Maps in Google, I see that I can import the file.

Sure enough, all 5,323 locations from my family tree are now on this one map! I've never been to my 2nd great grandmother's hometown of Santa Paolina, Avellino. But when I get there, I can use Google Maps to pull up the precise location of the town church and step inside!

Family Tree Analyzer can put every single location from your family tree on one map—complete with names and dates.

To get to Google My Maps, start at google.com/maps and click Saved in the left menu. Then click Maps and Open My Maps. I've created maps before, but uploading thousands of locations at once is fantastic! I can click any location to see who's associated with that place. There's also an option to open this map collection in Google Earth. This seems like the best way to see your places in living color, rather than basic map view.

Now I needed to turn my iPhone into my family tree navigator. I installed Google Earth and put Family Tree Analyzer's exported places file on my phone. In Google Earth, I chose Projects, then Open, then Import KML file. (That's the format of the FTA locations file.)

Now no matter where I am, I can open Google Earth and zoom out see which family tree locations are nearby. Then I can tap any map pin to see what happened there. Don't you want to have this on your phone?

And speaking of map projects:

• Which Global Map is Best for Genealogists?
• Your Ancestor's Location is Critically Important
• Prepare to Walk Along Your Ancestors' Streets

How to Add or Delete Custom Facts in Your Family Tree

I'm still busy making every source citation in my family tree complete and consistent. (See "Take the Time to Improve the Sources in Your Family Tree.") It's been so rewarding! Revisiting the documents and families tied to each citation shows me where I need more research. Sometimes it reminds me of past discoveries or problems.

One citation I reviewed was unique for my family tree. I realized I had a decision to make. I needed a custom fact type to handle a convict in the family.

You can create your own custom fact types in 3 steps with FamilyTree Maker. Your software should have this option, too.

This one citation covered 3 images and facts belonging to a man name Frank. Frank's brother married my husband's aunt, and I'd forgotten about my past discovery. Frank committed an unspeakable crime and was sentenced to 7 years in prison.

• He went to San Quentin State Prison on 18 June 1942 at the age of 21.
• He was transferred to the prison in Chino, California, a year later.
• He was released on 18 March 1947 with parole.

How would you enter these dates in your family tree? It seems I assigned these dates to a fact type I made up—Internment. But that custom fact type is for Japanese family members the U.S. shipped off to the middle of nowhere during World War II.

I needed another fact type for Frank, so I created one called Imprisonment. Right now, only Frank uses this fact type, but I'm still reviewing my family tree.

Identifying Custom Fact Types

I wondered if I'd used Internment for other non-internment facts. To find out, I exported a new GEDCOM file and opened it with Family Tree Analyzer (FTA). On the Main Lists tab of FTA, I clicked the Custom Facts tab.

FTA showed me 7 custom fact types used in my tree:

• Ahnentafel—I think this fact type should be part of the GEDCOM standard. I use it to identify all my direct ancestors.
• AKA (Also Known As)—for entering nicknames. This is standard in Family Tree Maker, but FTA doesn't recognize it.
• Event—this is so generic. Too generic.
• Imprisonment
• Internment
• Passport Application
• Visa—some ship manifests include facts about travel visas.

While looking at this table in FTA, you can double-click any row to see who is using this fact type.

Don't know if you have any custom fact types in your tree? Use Family Tree Analyzer to spot them.

I had one person using a fact type called Event. What the heck was that? I double-clicked the row to see the name, then I went to the person in my tree. Ironically, the Event was another man's prison stay. I guess I've struggled with how to categorize jail facts before. I switched this fact type from Event to Imprisonment.

There were 6 people with a custom fact type of Visa. Were these all visa applications for travelers? I double-clicked the Visa row, saw the names, and checked them out in my tree. Each one was a tiny entry pulled from a ship manifest. Obviously I don't add this fact to my tree routinely since there are only 6. But I'll leave them there in case these documents become available some day.

The 2 Passport Application facts were appropriate, but I know I have more than 2 passport applications. I'll bet I forgot I created a custom fact type for them!

The fact type that interests me most is the 35 people using the custom AKA fact type. I don't want to use AKA anymore. I've already started using a different style of recording name variations.

If they call someone by a different name on one census, I note it in the description field of their Residence fact for that year. My Aunt Elsie is a good example. I knew her all my life. I'm the baby she's holding in her profile photo in my tree. It came as a big surprise to discover her given name wasn't Elsie. It was Agnes! She's first called Elsie in the 1940 census, so that's where I've placed the name Elsie. It's in the description field of her 1940 Residence fact: "She is called Elsie."

Want to change how you record certain facts? Family Tree Maker can show you exactly where to find them.

I've reviewed my 35 uses of the AKA fact type and dealt with them all in the proper description field.

This is what's nice about reviewing all your citations at once. You can bring every fact you've ever added to your tree up to your current standards.

Add or Delete Custom Fact Types

To add a new fact type in Family Tree Maker:

• Click the Edit menu and choose Manage Facts.
• In the Manage Facts window, click New to create a new fact type.
• Type in a descriptive fact label so you'll understand what it is. The program will create its short label and 3-letter abbreviation automatically.
• Choose whether to share the fact (like a marriage fact), or give it only to an individual.
• Choose what you intend to fill in. Do you want to have a date and place or only a description? You can even make this fact private by default.
  
• Click OK.

Now when you want to use this type of fact, you'll find it in the Add fact drop-down menu.

To delete an unused custom fact type in Family Tree Maker:

• Click the Edit menu and choose Manage Facts.
• In the Manage Facts window, select the fact type and click the Delete button.
• Click Yes to confirm, and the fact type is gone.

Uh oh. I'm seeing something for the first time in the Manage Facts window. You can select any fact type, click the Data Options button, and see a list of every fact you've assigned to that fact type. To my surprise, this method finds another 36 people using AKA. I need to update them with my new style.

As I was writing this article, Family Tree Maker released a free update affecting the Manage Relationships option on the Edit menu. (Find out everything new in this version 24.1 release.) I haven't explored any of the Manage options before because I had the wrong idea of what they were. Now I know what to write about next week.

Report Finds Marriage Mishaps in Your Family Tree

Anytime you do a lot of work on your family tree, it's a smart idea to let Family Tree Analyzer have a look at it. This free software seems to offer me a new way to dissect my GEDCOM file each time I use it. And I've been doing a lot of work on my tree recently.

Last week I finished perfecting the citations in my family tree for these sources:

• 1851 England Census
• 1861 Census of Canada
• 1861 England Census
• 1871 England Census
• 1880 U.S. Federal Census
• 1881 England Census
• 1891 England Census
• 1900 U.S. Federal Census
• 1901 England Census
• 1905 New York State Census
• 1910 U.S. Federal Census
• 1911 England Census
• 1915 New York State Census
• 1920 U.S. Federal Census
• 1925 New York State Census

That adds up to 944 citations shared among family members found on the same census. Before I fixed them, a few sources had more than 700 citations each due to a catastrophic sync failure with my tree on Ancestry.com. I've given up trying to sync, but by next year I'll upload a clean version of my tree using a new tree name. I won't sync with it once it's uploaded.

Time for a Quick Check-Up

After all that editing, I wanted to see what Family Tree Analyzer (FTA) thinks of my latest GEDCOM file.

My GEDCOM Stats in FTAnalyzer had a strange line item telling me my family tree had some errors.

When you open your GEDCOM in FTA, you get a summary screen filled with basic facts about your tree. This time, I spotted something unusual. FTA said I had 4 lone individuals listed as single families. I needed to find them and see what was going on.

I found them by doing something I hadn't tried before. Usually I click FTA's Main Lists tab which opens to the Individuals tab. This lists everyone in your tree. But this time I clicked the Families tab next to the Individuals tab. I scrolled way to the right and found a column called Family Size. I sorted the data in that column from A to Z, putting all the families with a size of 1 at the top of the list. To my surprise, there were 41 families of 1.

5 Types of "Marriage Problems"

I opened my Family Tree Maker file and found each person from the FTA list, one-by-one. These "families of 1" fell into the following categories:

1. An unwed parent whose child's name you know from their birth record. In these cases, there's nothing you need to do. It really is a single-person family with a child.
2. Someone you meant to delete from the file but overlooked. Before you delete them, delete any of their citations or images. And detach them from an Unknown Spouse* if necessary.
3. Someone whose parents you deleted because you don't want to trace their family. (That's my in-law rule in action.) You may need to detach them from unknown parents. Otherwise leave them be.
4. Someone with a marriage date but no spouse. Take the time to search for the source of this incomplete fact and add their spouse. I've found Italian birth records with a marriage date, but no spouse's name!
5. A complete mystery, unattached to anyone, who you may as well delete.

*Unknown Spouse—As I worked through the list of 41 people, I found that many had an Unknown Spouse attached to them. Even babies who died young had these mysterious spouses. To see the unknown spouse in Family Tree Maker, go to a person's detail page. Then click Relationships rather than Facts or Timeline. If there is a partial marriage fact, delete it. Then detach the individual from their unknown spouse. Now the phantom spouse is gone from your file.

How many of these lurkers are hiding in your family tree? Here's how to find and eliminate them.

When I finished dealing with the 41 people with a family size of 1, I exported a new GEDCOM. Then I opened it in Family Tree Analyzer. Now I have 9 people with a family size of 1 because I made the decision to keep each of them. (Almost all are single parents.) The initial message from FTA saying I had 4 lone individuals listed as single families is gone.

This week I'll tackle my 1930, 1940, and 1950 U.S. Federal Census citations. Then I want to jump straight to the passenger lists of people coming through Ellis Island. Most of the immigrants in my family tree arrived in New York, so this is an important source to whip into shape. Then I'll continue working through my sources in alphabetical order.

After that, I have to deal with my countless Italian document citations. That's fine—I've wanted to work on those for a long time.

How Healthy is Your Family Tree?

If you've been working on your family tree for a while, you've no doubt gotten better at it with practice. That means your earliest work isn't as good as it should be. In my case, I know that censuses and ship manifests for my closest relatives are what I added first. And I'm fixing them as I work my way through my citations.

How did you begin your family tree? Were you searching for certain types of documents  first, like me? Did you begin with an inherited tree that someone else created? Take a look at the different reports FTA can offer you, such as:

• One Report, Endless Possibilities for Improving Your Family Tree
• Let Family Tree Analyzer Find Your Duplicates Duplicates
• 4 Problems You Can Fix with Family Tree Analyzer

Pluck the Stragglers Out of Your Family Tree

I love when someone finds their family in my online tree and contacts me. Last week I heard from a new-found 4th cousin.

More often our connection is distant—cobbled together through the relatives of in-laws. I had this type of connection last week, too. A woman found her grandmother in my tree and wanted to know what else I could tell her.

I told her everything came from the 1920 census and a few New York City death certificates. But I had nothing else to offer.

In fact, as I wrote in my reply, she shouldn't be in my family tree at all. I explained that her grandmother's sister married a man named Celentano. That man's uncle married my grandmother's 1st cousin, Consiglia Sarracino.

I knew from the names Celentano and Sarracino that this was some of my earliest family tree research. When I started, I followed every possible thread for my American cousins.

I used censuses to stretch out the Celentano family as far as I could. And then I built out the families of the people who married into the family. That's how her grandmother wound up in my tree.

Enforcing the In-Law Rule

It wasn't until much later in my genealogy life that I created an in-law rule:

I will not add anything to an in-law's profile beyond their facts and their parents' facts UNLESS my cousin asks me to research that family.^*

^*This rule does not apply to my Italian research where entire towns are inter-related.

Establish a rule to keep your family tree on the path you want.

How many other far-flung in-law branches are still in my family tree? How can I find them in my enormous file?

I explored Family Tree Analyzer software for a while, but it wasn't a shortcut. Maybe there is no shortcut.

Stragglers in my tree would come from my parents' and grandparents' generations. Those are the people I would have found in my early census searches.

Most of my close cousins are from my maternal grandmother's family. In my earliest days, I would have spent time on the families of Grandma's aunts and uncles, the Saviano family.

This is a manageable group to work with. Grandma had only 3 Saviano aunts or uncles who lived long enough to marry and have children.

Uncle Semplicio

As a little girl, my mom was afraid of her great uncle Semplicio. He was an older man with one eye. He literally lived in a closet next to her apartment for a while.

Long ago I met someone online with a connection to Semplicio's wife Giovina. With his encouragement, I built an enormous tree for Zia Giovina. Once I decided to follow my in-law rule, I cut out every relative but Zia Giovina's parents.

Looking in Family Tree Maker, I see families for 3 of Semplicio and Giovina's children. I can view each family to see if I need to delete anyone. Nope. Everyone was following the in-law rule.

Aunt Filomena

My grandmother's aunt is an example of going out of my way to document an in-law. But I want it this way. One of her grandsons is very interested in our family history, and he helped me with it.

Plus, Filomena's husband came from a town very close to Filomena's Italian hometown. There may be a family tie somewhere in their past!

Uncle Raffaele

Uncle Raffaele died long before I was born, but his wife Lucia was sometimes at family gatherings. My brother and I knew her and Aunt Filomena as "Zee Loo Gee" (Zia Lucia) and "Zee Vulla Men" (Zia Filomena). We never saw Zee Vulla Men without Zee Loo Gee.

I have extended families for Raffaele and Lucia's children in my family tree. Clicking through to view them all, I found only one in-law family I should delete. I do want to preserve the research, but not in my main tree. I'll follow my own advice and export this group of people to a new tree before deleting them from mine. (See "How to Export and Delete Branches from Your Family Tree.")

Exporting the 46-person branch was easy, but it didn't seem to capture the media files. I'll do that myself. My document tracker file will help me see which media files belong to this batch of people.

Deleting the branch was tricky. There wasn't one ancestor whose descendants capture the whole group. Instead, I worked my way through the families, noting all their media files. Then I viewed a family tree chart for each group and deleted them from my family tree.

I made sure all the right media files were no longer in my main tree, and I exported a new GEDCOM from Family Tree Maker. A GEDCOM is a text file that follows a standard format that any family tree software can understand. I opened the GEDCOM with Family Tree Analyzer to see if I missed anyone. Would FTA find unrelated people from this branch still in my family tree?

If your family tree is big, Family Tree Analyzer can narrow it down to certain types of names for you.

Here's how to check:

• Launch Family Tree Analyzer and open your latest GEDCOM.
• Go to the Main Lists tab to see everyone in your tree on the Individuals tab.
• To exclude close family and true cousins from this search:
  • Scroll to the right to find the Relation to Root column.
  • Click the arrow button at the top of the column to open a small window.
  • Unclick Select All, then click to select only the blank field at the top of the list.
  • Click the Filter button to close the small window.
• Scroll all the way left to find the Surname column.
• Click the arrow button at the top of the column and choose Sort A to Z.
• Browse the shorter list for the last names you don't want to find.

Success! I didn't find anyone who wasn't supposed to be there. Now I can backup and save my Family Tree Maker file.

But I'm not really done, of course. I have some cousins through my paternal grandmother, and her mother had a bunch of brothers. I can run through this same process with that branch and a few others.

Should You Do This, Too?

The main reasons for going through this export/delete process are:

• to stop misleading people into thinking you're their blood relative
• to stop spending time on branches that aren't the focus of your family tree
• to conserve computer resources.

Plus, I don't like it when I see a name in my tree index and think, "Who on earth is that?"

Take These Steps to Be Ready for the 1950 Census

When they release the 1950 United States Census on April 1st, will you be ready to find your family? It will take a few weeks for the collection to be fully indexed and searchable. But don't let that stop you.

With very little trouble, you can create a list of who you want to search for. Then you can prioritize your list and use an online tool to tell you where to look.

Create Your Search List

Once again, it's Family Tree Analyzer to the rescue. Here are the steps I followed to create my list of 1,045 people who may be in the 1950 U.S. census:

1. Export a GEDCOM file from your family tree. Your family tree software or the website where you keep it should have this option.

2. Launch Family Tree Analyzer and open your GEDCOM file.

3. Click the Main List tab, then choose Individuals to Excel from the Export menu at the top.

This saves the file in CSV format. I find it's better to save the CSV file in your spreadsheet software format. For me, that's Excel. This will give you more functionality and let you save your formatting, like column widths.

You can delete several columns for simplicity. All you really need is:

• Forename
• Surname
• BirthDate
• BirthLocation
• DeathDate
• RelationToRoot

4. Sort the data by the BirthLocation column, then hide (or delete) the lines for anyone who didn't live in the USA. Make this column nice and wide so you can see the country.

This step took a while for me because I have about 36,000 people in my family tree who never came to America.

Keep your immigrant ancestors in mind. I realize I've hidden the lines for my grandfathers and my great grandparents. I know I won't forget them, but I will put their lines back in.

Follow these few steps today and be completely ready for the upcoming release of the 1950 U.S. census.

5. If you hid the non-U.S. lines, copy the entire worksheet to a new, blank worksheet. The hidden lines will not copy. If you deleted the lines, go to step 6.

6. Sort the data by the BirthDate column, then hide (or delete) the lines for anyone born before 1850 and after 1950.

7. Sort the data by the DeathDate column, then hide (or delete) the lines for anyone who died before 1950.

8. If you hid the out-of-range lines in step 7, copy the entire worksheet to a new, blank worksheet. The hidden lines will not copy. If you deleted the lines, go to step 9.

Now you have a list of all the people in your family tree who may be in the 1950 census.

9. Sort the data by the RelationToRoot column so you can focus on your closest relatives first.

When they release the census and you start your search, you can hide or delete lines as you find people. I'm going to add a new column to my spreadsheet where I can put an X when I've found someone.

Find the Neighborhood Before the Index is Ready

I know I want to find my parents first. They made their first appearance in the 1940 census, so now I want their families in 1950.

To find the right set of census pages to scour for their families, follow these steps:

1. Go to stevemorse.org and select Unified 1880-1950 Census ED Finder from the US Census menu.

2. See what address you have for the family in the 1940 census and enter that on the stevemorse.org website.

I'll set the State to New York, the County to Bronx, the City or Town to Bronx. Then I'll enter the House Number 260, and choose East 151st Street from the pull-down list. Next I'll click the "see google map" button to view this address on the map. You need this so you can see what the surrounding streets are.

3. Select the nearest cross or back street from the pull-down menu. Repeat this step as needed.

4. Look beneath the street names you've chosen. You'll see how much you've narrowed down the possible enumeration districts.

Don't wait for the 1950 census to be indexed. Use this tool to go to the right set of pages.

In my case, my mom's family will be in one of two enumeration districts. I can easily go through them page-by-page when the images are available. In fact, since the majority of my relatives lived right there, I'll be on the lookout for any familiar names.

So you see, with very little effort, you can be ready for the April 1st release date. You'll have your list, and you'll have your priority people. The best thing about this spreadsheet is it'll help make sure you don't overlook anyone.

Be thankful we're getting access to 1950 in 2022, at the end of the 72-year privacy period. People in the U.K. just got access to their 1921 census!

How to Find the True Cousins in Your Family Tree

I've been on a genealogy rampage lately—but in a good way. I'm tapping into my enormous database of vital records from my ancestral hometowns. And I'm using it to add about 100 people a day to my family tree.

Everyone from my ancestors' hometowns can fit into my family tree somehow. But right now, I'm going after my distant cousins. Here's how I'm doing it:

• I pick one of my direct ancestors, like a 4th great grandfather.
• I locate every one of their children.
• I find out who each child married, and I search for their children.
• I keep searching for children's children until I reach the end of the available vital records.

It's a blast to add whole families to my tree that some distant cousin is going to find through an Ancestry hint.

What happens when you research your ancestors siblings? Your family tree grows to include hundreds or thousands of blood relatives.

With all this recent growth, as of this writing, I have 36,434 people in my tree. Many of them have crazy relationships to me. Like step-father of the son-in-law of the 2nd great uncle of my great aunt's husband.

Now that I'm concentrating on blood relatives, I wondered how many of each type of cousin I've located. How many 1st cousins 3 times removed have I found? How many 3rd cousins 4 times removed?

To find out, I exported a current GEDCOM from my Family Tree Maker file. (Make sure you are the root person in your GEDCOM file.) Then I opened it with Family Tree Analyzer. I clicked Main Lists to see a spreadsheet view of everyone in my family tree. Then I clicked the Export menu at the top of the program and chose Individuals to Excel.

In one second flat, I had a spreadsheet with all the facts and people from my tree! I opened the file and sorted it by the RelationToRoot column. Then I filtered out any blank relationships, hiding them from view. (Family Tree Analyzer doesn't include crazy relationships like the one I mentioned above.)

Use Family Tree Analyzer to instantly export all your family tree facts to a spreadsheet. Then sort and filter to see how many types of cousins you've found.

Now I can click with my mouse and pull it down to select relationships of the same kind. Then I can see at the bottom of the spreadsheet how many rows I've selected. Here's what I have.

I'm using an abbreviation below that I learned from another genealogist. C means cousin and R means removed, so 1C3R is a 1st cousin 3 times removed.

# of First Cousins in my family tree:

• 1C–5
• 1C1R–30
• 1C2R–108
• 1C3R–97
• 1C4R–190
• 1C5R–259
• 1C6R–166
• 1C7R–65
• 1C8R–10

# of Second Cousins in my family tree:

• 2C–44
• 2C1R–172
• 2C2R–29
• 2C3R–193
• 2C4R–439
• 2C5R–339
• 2C6R–114
• 2C7R–15

# of Third Cousins in my family tree:

• 3C–101
• 3C1R—112
• 3C2R—116
• 3C3R—556 Whoa!
• 3C4R—485
• 3C5R—179
• 3C6R—29

# of Fourth Cousins in my family tree:

• 4C–18
• 4C1R–21
• 4C2R–215
• 4C3R–361
• 4C4R–205
• 4C5R–44

# of Fifth Cousins in my family tree:

• 5C–16
• 5C1R–86
• 5C2R–159
• 5C3R–70
• 5C4R–44

# of Sixth Cousins in my family tree:

• 6C–19
• 6C1R–28
• 6C2R–16
• 6C3R–20

# of Seventh Cousins in my family tree:

• 7C–9
• 7C1R–6
• 7C2R–3

# of Grand Aunts and Uncles in my family tree:

• grandaunts and uncles–14
• 1st great grandaunts and uncles–46
• 2nd great grandaunts and uncles–68
• 3rd great grandaunts and uncles–103
• 4th great grandaunts and uncles–89
• 5th great grandaunts and uncles–77
• 6th great grandaunts and uncles–77
• 7th great grandaunts and uncles–9

# of Great Grandparents in my family tree:

• 1st great grandparents–8
• 2nd great grandparents–16
• 3rd great grandparents–31 only 1 missing!
• 4th great grandparents–53
• 5th great grandparents–84
• 6th great grandparents–108
• 7th great grandparents–72
• 8th great grandparents–20
• 9th great grandparents–5

I love seeing this breakdown of my people. I'm astonished to learn that I've identified three of my seventh cousins twice removed. The only thing keeping me from finding 8th cousins is a lack of records. But I'm psyched to keep adding more and more cousins. And their spouses. And their spouses' families.

You say you don't venture beyond your direct ancestors? These cousins are your people, too. Does everyone ask you if you've finished your family tree yet? Tell them you have several hundred cousins still to find. And their spouses. And their spouses' families. Tell them this is one puzzle that's never finished!

Find out what else you can do with Family Tree Analyzer:

• 4 Problems You Can Fix with Family Tree Analyzer
• Did I Find a Scandal in My Family Tree?
• Let Family Tree Analyzer Find Your Duplicates Duplicates

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.

4 Problems You Can Fix with Family Tree Analyzer

Want to find mistakes you didn't know you made in your family tree? Launch the free software called Family Tree Analyzer. Export a GEDCOM file from your family tree software or the website where you keep your tree. Then open the GEDCOM in Family Tree Analyzer.

When your file is open and processed, you'll see a screen full of facts about your family tree. For instance, my tree has 326 sources, 31,775 people, and 11,494 families. Wow! Next comes a breakdown of everyone's relationship to me, the home person in the family tree:

• Direct Ancestors: 411. Uh oh. Last week I counted 403 direct ancestors. Did I miss eight, or are those my double ancestors? (My paternal grandparents were 3rd cousins with shared ancestors.)
• Descendants: 2. Hi, kids.
• Blood Relations: 4,802. That's a lot of blood.
• Married to Blood or Direct Relation: 1,877. These are the immediate in-laws.
• Related by Marriage: 19,283. Yup, my ancestral hometowns were full of intermarriage.
• Linked through Marriages: 5,225. I go off on a lot of tangents.
• Unknown relation: 175. I carry some unrelated people because I know there's a connection somewhere. But 175 seems high.

I had another reason for launching Family Tree Analyzer today. But right now I have two potential problems to investigate:

• The number of direct ancestors.
• The number of unknown relations.

To find out more about these issues, click the Main Lists tab to open the very useful Individuals table.

Problem 1: The Number of Direct Ancestors

As you scroll to the right in the Individuals table, you'll find a column labelled Relation to Root. Start with "2nd great grandfather." This takes a lot of scrolling in a big family tree. You'll find your 1st great grandparents under "great grandfather" and "great grandmother."

Even custom facts you create can be used and checked with Family Tree Analyzer.

In my case, I need to see if any of my great grandparents are missing their custom fact I called Ahnentafel. I use this custom fact in Family Tree Maker to view only my direct ancestors in the index. That's how I counted 403 of them.

To see if the extra people are my double ancestors, I'll look for missing Ahnentafel numbers. I realize this is specific to my tree because of the Ahnentafel field. You may want to scan the list for misidentified people.

And, in fact, I didn't miss any of my direct ancestors. The difference in the number of direct ancestors must be because of my double ancestors.

Problem 2: The Unknown Relations

Going back to the Individuals table, scroll to the right and click the top of the Relation column to sort the table. Scroll down to the bottom to find all the Unknowns. Then scroll to the left to see their names.

In my case, I recognize a ton of the Unknowns. (see "How to Handle the Unrelated People in Your Family Tree.") They're related to a cousin Silvio whose exact relationship I can't determine. It's a dead end because of a lack of records from Silvio's hometown. So, here he sits in my tree, with a ton of direct relations, unrelated to me.

Next in the list I see a family group that I found in a 1742 census of my grandfather's hometown. But I never found their connection to me. I did a quick search of the tens of thousands of vital records on my computer for one member of this family. I found his death record! Now I can merge the two men named Gregorio Alderisio in my tree. His death record proves the connection by including the name of his wife and both parents, and his age at death.

That one death record converted 11 unrelated people in my family tree to distant cousins.

I found another family group that's unrelated to me, and I can't remember why I put them in my tree. I'll have to investigate further and decide if I should remove them. With Family Tree Analyzer, it's easy to find them when I'm ready to solve the problem.

Problem 3: Comments + Time = Discrepancies

The reason I wanted to see this report today is to find discrepancies in descriptions within my family tree. I'm thinking of how I type in different occupations for people.

Here's an unexpected way to find and fix inconsistencies in your family tree.

I'll sort the Individuals table by the Occupation column. My tree has tons of Italian job titles followed by an English translation in parentheses. Sometimes I see a multi-word job title that has an error. I want to find those in the list. Then I can see which people it's attached to, and go fix it in my family tree.

I found a few entries that must be what I call "Search and Replace victims." A long time ago, I decided to add an English translation to the Italian job titles. To do this, I used the search and replace function of Family Tree Maker. You have to be very careful with search and replace. You may wind up changing something you didn't want to change. And, of course, I'm scanning for typos in the English job titles.

Now I can go to these people in my tree and fix their occupation entries.

Problem 4: Unused Sources

Before we leave Family Tree Analyzer, there's one other thing to check. We've been looking at the Main Lists / Individuals table. Click Sources, two tabs to the right of Individuals. Now click to sort by the last column, FactCount. Do you have any sources in your family tree that are showing a zero fact count? I have five, so I want to investigate.

After taking a look at these sources in my family tree, I deleted four, but one actually had three uses. I don't know why it was in the list.

There's no end to the fixable problems you can discover using Family Tree Analyzer. Make it part of your routine to export a GEDCOM, say, once a quarter, and examine your tree with Family Tree Analyzer. It's a valuable safety net for your family history research.

And speaking of Family Tree Analyzer:

• How to Plug the Holes in Your Family Tree
• It's Time to Make Your Family Tree Clear and Consistent
• Run This Genealogy Report to Help Clean Up Your Dates