03 September 2024

6 Powerful Features of Family Tree Maker

A computer monitor displays a large number 6.
Most family tree software programs have more features than you may realize. These 6 features of Family Tree Maker are genealogy game-changers.

I bought my first computer—an actual IBM PC—in 1985 and upgraded from DOS to Windows 3.0 in 1990. I remember how juvenile early software programs looked. My first version of Family Tree Maker had that 1990s look when I got it in 2002.

Today, Family Tree Maker has an excellent, robust user interface. (See "Comparing Family Tree Programs Is an Eye Opener".) Here's a look at 6 FTM features I've found to be a big help in building your family tree. If you're using another program, does it have all these features?

1. Color Coding

I first used FTM's color-coding feature to distinguish the 4 main branches of my family tree. I went to each of my 4 grandparents and in one click, gave each one and all their direct ancestors a color. I made Grandpa Adamo and his ancestors green and Grandma Mary and her ancestors blue. I made Grandpa Pietro and his ancestors yellow and Grandma Lucy and her ancestors pink. My grandparents Pietro and Lucy were 3rd cousins. Their shared ancestors have both yellow and pink bars beneath their names.

These colors come in handy when I'm working on an individual whose relationship to me is unclear. When I view the person in FTM and see green, blue, yellow, or pink ancestors, I know exactly which ancestors we share.

For more ways to use color coding, see "Using Color to Understand Your Family's Last Names".

2. Filters

There are a few other groups for which I was using color coding. Then I realized there was a better way.

Family Tree Maker lets you create custom filters so you can display only a select group of people in your index. When your family tree gets pretty big, this can be a big help. What I didn't know at first is that you can assign a color code to everyone in a particular filter. You don't have to add the color to a person or family unit one at a time.

Here's why that's so helpful. I have 246 people in my family tree who have no direct relationship to me. Some share my Grandma Mary's last name, and they come from the same little town as her parents. But a lack of vital records means I can't figure out how we're related. At first I was color coding unrelated people in red. But if I discovered their connection, it was a bit tedious to remove the red color from the correct people. Now if new research turns them into relatives, I remove them from the Unrelated filter and the red color is gone.

In fact, I recently solved a mystery that turned 14 unrelated people into relatives. You never know when you'll find the answer to those unanswered questions. Now my Unrelated filter contains only 232 people.

I've also created filters for:

  • Everyone in my family tree with an Ahnentafel fact (more on Custom Facts in a moment). This restricts FTM's index to only my direct ancestors.
  • All the Italians I know emigrated to Brazil. This helps me connect to the many people in Brazil with my last name. This filter uses a blue color code.
  • All the DNA matches I've been able to place in my family tree. This filter uses a purple color code.
  • Actor Tony Danza's direct ancestors. (See "Apply Your Genealogy Superpower to Other Families".)
  • My Uncle Kenny's direct ancestors. He's my mother's sister's husband with roots in the same town as my father. I'm hoping to spot an ancestor overlap some day. This filter uses an orange color code.

To add a color to everyone in a filter, find Smart Filters in the lower left corner of FTM's Tree tab. Choose Manage Filters from the menu beside Smart Filters. Select the right filter and click a color. Done!

3. Custom Facts

When I learned about Ahnentafel numbers, I needed a way to add the right number to each ancestor in my family tree. FTM doesn't have an Ahnentafel fact, so I created it. (Discover the value of Ahnentafel numbers in "3 Things to Do with Ahnentafel Numbers".)

Over the years I've needed other custom facts, too. My husband's family is Japanese and from California. The U.S. government forced then into internment camps during World War II. There are documents for these people on Ancestry.com, so I needed a way to record dates and places. I created a custom fact called Internment. There's also at least one guy in my family tree with documents about his jail time. I created another Custom Fact called Imprisonment.

To find out how to add a custom fact in Family Tree Maker, see "How to Add or Delete Custom Facts in Your Family Tree".

4. Undocumented Facts Report

For months now, I've been creating source citations for the majority of people in my family tree. I knew this would be a huge task, so I started with the people who have no source citations at all.

Using Family Tree Analyzer, I generated a spreadsheet of people without source citations. I sorted the spreadsheet to put people with a blood relation to me at the top. They're my first priority. To find out how to create this spreadsheet, see "2 Keys to Tackling a Big Family Tree Project".

Working through everyone in this big spreadsheet is step one. Then I'll use a Family Tree Maker feature to see what I've missed. FTM has a report within the Source Reports category called Undocumented Facts. This will help me find people who have at least one source citation, but are missing others.

When the time comes, I'll export that report to Excel so I can again work on my closer relations first. I know there will be a lot of facts in that report that I'm not going to source:

  • I don't include a source for a person's sex. Unnecessary.
  • I can't cite a source for more recent events, like the birth of my niece's children, or even for my cousins' marriages.

I'll have to filter out and delete from the spreadsheet people whose facts I'm not going to cite. Meanwhile, I'll keep chipping away at the spreadsheet of "sourceless" people. I need to reduce the undocumented facts as much as I can before running that FTM report. Otherwise, with 81,492 people in my family tree, generating the report will take forever. In fact, I know it will. I'll have to generate the report in batches. I can choose one strategic person and run the report only on their extended family, not the entire tree. Mo' people, mo' problems.

5. Relationship Calculator

When someone writes to me because they found their ancestors in my family tree, I go right to this tool. FTM's Relationship Calculator gives me a clear understanding of a complex relationship.

When I heard from a man last week, I looked at his grandparents in my family tree. I used the Relationship Calculator to see who our common ancestors were. Then I turned to my relationship calculator spreadsheet (not part of FTM—I should have called it something else!) to see my relationship to the man who wrote to me. The spreadsheet says he's my 4th cousin once removed. And FTM's Relationship Calculator makes it clear who our shared ancestors are.

When you use the FTM tool, don't stop at the word description of your relationship. Click the View Relationship Chart button for a clear visual of the relationship. For an example of the Relationship Calculator tool in action, see "How to See Your Cousin Connections More Clearly". To download your own copy of the relationship calculator spreadsheet, see "Which Side the Cousin Falls On is Key".

6. Find and Replace

Anytime you use the find and replace feature of any software, you have to be careful. You may wind up changing part of a word, or even part of a name. Say I want to change an Italian man's occupation from "ferraro" to "ferraro (blackmith)". I must remember to make that change case sensitive. Otherwise anyone in my tree with the last name Ferraro will become ferraro (blackmith)!

The Find and Replace option is in the Edit menu of Family Tree Maker. I did use it to include English translations for the Italian occupations in my family tree. At least one of these changes went wrong. See "How to Handle Foreign Words in Your Family Tree" for other uses of Find and Replace.

You can restrict a Find and Replace operation by selecting or not selecting:

  • Match case (change ferraro, not Ferraro)
  • Find whole words only (don't change a word if it's part of another word)
  • Use wildcards (*?); this could be trouble, so use with care.

You can also tell FTM only to make a change if it finds the text in:

  • Facts
  • Media
  • Notes
  • Tasks
  • Sources

There's a final option of Places, but it's unavailable to me.

There have been a couple of times when I realized I was using the wrong spelling of a last name. For instance, I found the name Aucone in several old vital records, but I thought it said Ancone. I searched for the name in the Italian White Pages and the Cognomix website. Now I know Aucone is the correct spelling.

Before I do a find and replace, I have to think. Could another name in my family tree contain the same letters as Ancone? To be safe, I can select the Match case option to change all instances of Ancone to Aucone.


Sometimes you don't realize you need a software feature until you read about ways to use it. I hope this article encourages you to dig deeper and explore your family tree software.

4 comments:

  1. I have been using FTM for many years after using PAF, it was the closest to the PAF program in entering data. I have never used any of these options that you have given. THANK YOU!!!

    ReplyDelete
    Replies
    1. That makes me so happy. I learned some of FTM's features only after someone else talked about them.

      Delete
  2. I use FTM as well and like each of the features you mentioned. One thing to keep in mind is the long-time bug in the Relationship Calculator (it's been there since Ancestry owned it and no movement by MacKiev to fix it). The FTM Facebook group list many of the particulars of the bug, but the basic premise is when you have multiple paths to the same MCRA and the path lengths are of a different value (say one way is 4th GGP and the other is 3rd GGP). The longer path will be inaccurate for at least 3 generations, showing xGreatUncle or xGreatAunt, then Spouse of X and other entries. The longer the path backwards, the worse the problem. Plenty of tickets submitted and MacKiev acknowledging it's a bug.

    Another feature I like about FTM is the ability to have Progeny's Charting Companion integrated into it as a real time reporting tool, whereas other software packages will require you to export to a GEDCOM, then import into Charting Companion, and then run your report. Nice time saver.

    A cool feature that FTM and Charting Companion possess, is the ability to print a McGuire Chart for DNA Analysis. Charting Companion calls it a DNA Matrix and it can be found at https://progenygenealogy.com/products/Family-Tree-Charts/DNA-Matrix/

    One thing I do not like about FTM is that neither FTM nor Progeny's Charting Companion will let you print an interfamilial family tree, so if a common ancestor is in your tree say 3 times, that person will display 3 times in 3 different parts of the tree (no interconnecting lines). Charting Companion will let you display a "cousin stub" to indicate that a person can be found elsewhere, but if you have lots of endogamy and pedigree collapse in your chart, it's pretty much unreadable. Works fine for a common cousin relationship when you have a few.

    If you need to print an interfamilial tree, the only 2 solutions I know of are to either export your tree to a GEDCOM and import into Exploring Family Trees at https://learnforeverlearn.com/ancestors/ or to use GRAMPS family tree software, which is free and found at https://gramps-project.org/blog/ GRAMPS will produce an interfamilial tree from the imported GEDCOM, it's one of their free GRAMPLETS that you load.

    Another thing I do not like about FTM is their continued adherence to the old GEDCOM 4 standard for locations of city, county, state, country, which works great for Salt Lake City where the software originated, but not for Munich or other places in Germany which have a variable 3-6 level administrative hierarchy, or France, which just changed their hierarchy a few years ago, or many other countries. My solution there is to use GRAMPS, which stores locations by GPS code, so you can build a table showing the administration hierarchy for the time period in question, which avoids the historical versus current location issue, and in a place that changed hands after wars frequently, such as Alsace, you can build a large table and use different languages for the appropriate time period.

    I synch regularly with my family group between FTM and Ancestry, using FTM for its many tools (which are quite good) as the "consistency czar' for our group. Our final product is ported periodically over to GRAMPS for reporting and DNA analysis.

    Love your blog and I read it every week!

    ReplyDelete
    Replies
    1. Thanks, Jon, for making so many excellent points. I'm certainly going to follow through on your leads.

      Delete