macOS Big Sur Compatibility for Family Tree Maker

macOS Big Sur Compatibility for Family Tree Maker

I recommend that you read this Knowledge Base Article for Software MacKiev

https://support.mackiev.com/944428-macOS-Big-Sur-Compatibility-for-Family-Tree-Maker

____________________________________________________________
Copyright © 2020 by Cousin Russ

macOS Catalina Compatibility for Family Tree Maker

If you are a Mac user, I suggest that you read this Knowledge Base article at familytreemaker.com

macOS Catalina Compatibility for Family Tree Maker
____________________________________________________________
Copyright © 2019 by Cousin Russ

Undocumented Fact Report Management

I understand that many users don't care about Sources and Citations. Over the years, I have learned how important they are. I have also learned how to manage that issue. I want ALL Facts with a Citation, even those Facts that I create and the I use for my purposes to maintain the file.

Working with two (2) new files, in the past three years, I learned to run the Undocumented Fact Report Daily. By doing so, and I can keep this issue under control. That is FIX the issue, based on the work that I did that day.

I took those two files and merged them into my Master database. That experience is a whole other topic. Because for the past two or three years I was in the habit of running the Undocumented Fact Report I ran it for the first time in my Master database. What I ended up with was a 169 PAGE Report. Shocked, to say the least.

To run this report, go to the Publish Workspace, select the Source Report in the Collection Tab, select Undocumented Facts, then Create Report.

When the "Create Report" button is selected, I want to make sure ALL Individuals are included.

Then I realized one problem that really brought the importance of this report. A change, many versions ago, about the "Sex" Fact had been changed requiring a Citation. Many Records either state that as a fact or can infer that fact, and should be documented. Family Names / Given Names are not always obvious. So we were given the Citation field for that Fact.

That second image is the clue /  reminder to me as to why there were so many pages of Undocumented Facts. I have some clean up work to do. I had to develop a Plan to deal with all of these Undocumented Facts. What I was NOT going to do, is clean them all up right now.

As you may know, we can Edit the Profile, from the Report, by double clicking on the Name (that is bolded) and the Person View will appear.

The Sex Fact does not have a Citation, but the Name Fact does have a citation, This is a quick and easy way to resolve this problem, Copy the Citation from the Name Fact, and Paste Link to Source Citation. The Copy source citation is the ICON to the Right of the "New" and left of the Edit (Pencil) ICON. That is the Family Tree Maker Clipboard (not Windows Clipboard)

Then select the "Sex" Fact, and Past Link to Source Citation.

That process will take care of those Facts that did not require a citation from previous versions. Easy but time consuming and needs to be done.

BUT, the next profile had other Facts that did not have Citations. From my analysis since I started this clean up project, over the many versions of Family Tree Maker, some Citations were lost and / or unlinked from Facts. So I needed a PLAN.

My plan is to use the Filter Feature to help me manage those profiles that have one or many Facts without a Citation. To do that, I created a "No Documentation" Fact. That way, I can Filter In or Filter Out, anyone with the No Documentation Fact. The name of the fact is not important, that was just the one I chose.

Keeping in the Undocumented Fact Report, I would ADD that Fact to every person in that report AND put a Citation on that Fact. Here is my citation (Reference Note)

Worthington, Russ, [ ADDRESS FOR PERSONAL USE, ], File Citations; This is a "No Documentation" citation, where there are no citations on Facts.

As I started to go through this process, three things were seen.

1. No Citations on any Facts in that profile
2. Only ONE Fact without a Citation
3. A number of Facts without a Citation

Number 1 was may be a large problem, as there is not clue, on that screen to tell me where that information came from. More time involved, but in the People Workspace, Person View, looking at other information, especially a spouse, parents, or children. Clearly not in the report.

It became clear, that this phase of the project is to Mark All Profiles with a Citation issue. 

Number 2 and 3 are a little easier, in that I have at least ONE Citation on other Facts. I can review those citations to see if that record addresses the Fact(s) that are not documented. The Only one fact, should be an easy fix.

This is time consuming, but here is where the Filter In / Filter Out feature comes in very handy.

Lets say I added the No Documentation Fact to the First Page in the Report. I can now go back to the "Individuals to Include". Select ALL, Filter OUT, select the "No Documentation Fact", Any Data, and those profiles with that Fact will be removed from the report.

For me, this does a couple of things, Lets me focus on the easy fixes, or the ones that will take more time, and I can resolve that one fact that doesn't have the citation from previous versions of the program.

In looking at the Undocumented Fact Report, it became obvious which Profiles had that one fact, not documented. It included on the Name and the Fact.

I can fix them right then and there, as noted above.

Once all of the Undocumented Facts are identified what the No Documentation Fact, I can then get back to research and when I come across a Profile with that FACT, I can deal that that undocumented fact then, because I can see it in the List of Facts.

I marked the No Documentation Fact as Private, so only I can see it. In this example, I do not know the persons Name, (5 underscores), but when I look at the full profile, I see that this is a Spouse of someone in my database. I can look at the Citations for the Spouse, to pick up the Citation for this person, that has NO Citations on either Fact.

The No Documentation in the Fact Description field, may be an easy fix, or may be  not so easy.

My goal is to KNOW who has one or more Facts that are not documented. Using the Filter In / Filter Out feature, and get that Undocumented Fact report to Zero, then I can go back to my research. AND I can also go to the People Workspace, and use the Filter In Feature, to Filter IN all who have the No Documentation Fact, and further include, if I want, the No Documentation, Undocumented Fact, or Undocumented Facts in the description.

NOW, once I have all of the Facts documented in the Profile, I can DELETE that No Documentation Fact from that Profile. Now running the Undocumented Fact Report is important to be run frequently, with the goal of No / Zero profiles on that report (again, filtering out the No Documentation Fact).

Lesson Leaned: Run the Undocumented Fact Report daily
____________________________________________________________
Copyright © 2019 by Cousin Russ

Reader Question: Purpose of the Fact Description field

Another User Question (love these questions)

What kind of information goes in the “description” tab and does that information eventually migrate to the “notes” section?

This is a great question. "It depends" is my quick answer.

Each FACT that is created in Family Tree Maker has Three (3) FIELDS. You can see the Facts in your File, in the Edit Menu, Manage Facts item.

That will bring up a list of All of the Facts that you are using, and where you will Select the Fact you want to Edit, or one of the Places where you can Add a New Fact. You can always Add a New Fact in the People Workspace, Person View, which is where I would add a new fact.

In this case, I selected Address. It is an Individual Fact, that can be shared with any other Profile. You will note the Annulment Fact, which IS Shared. So, you enter that Shared Fact, and it can be Shared with only a Spouse. Most Facts are Individual. 

I chose Address, because you might think that many profiles might use that Address. That is True, but the "shared" fact is not broad enough, and it only intend for a "married" couple. Married defined in the Marriage Fact settings, which does mean that the couple of married. That is a topic for another blog post.

I am going to click on the Fact, Properties button:

And we have Choices on what Fields we want to have with that Fact. Date / Place Fields, Date / Place / Description Fields, Description Only.

The default for this (system created Fact) is Date / Place / Description, which makes sense, right?

Below that is "Fact sentence". There is where you can change that the Fact will look like in a Genealogy Report. Below that is an Example of that that Fact Sentence Looks like.

You will notice that I marked this FACT as "Private by default". I do not want the Address Fact in my Online Tree. I want to see it always in my File, just not online. So, every time I Add an Address Fact, to a Profile it will be marked Private.

The question was, what do I put in the Fact Description?

Before the Places Workspace was improved, I would put the Street Address into the Description Field. With the option to use the Historical Place Name option, I put the Full Street Address in the Places Field.

Here is an example from a Profile.

There are four (4) Address Facts. Each with a Date, Place, but the description field is blank (image to follow). I point this one out for a reason. I have 2 Citations on the 1917 Fact, World War I draft), 1930 and 1940 Census Records, and a 1942 Fact, which was a World War II draft record).  That was this persons residence, from those records over time. I mention Census, because I use the Residence Fact, with Citations to the Census RECORD. But, these two census records had the street address. Here is why I do it this way. Who else lived at that address ?

Seven (7) People lived at that address over time. The use of the Historical Name is how this works.

You will notice that the address is in that upper field.

What is not in my earlier screen capture, is the Zip Code. Why didn't I enter is. Answer: It was NOT in the Record. If I have or know of the Zip Code, like from an Public Record RECORD, I would put that in the Description Field.

This is the image, mentioned earlier, from the People Workspace, Person View. I  entered the Date, and the complete address, on that 1940 Census Record. Not the "Lock" or Privacy setting.

The Options, on the screen capture, is another place where you can Change the Properties for that, or any Fact.

The final question ask, Migration to Notes. NO. All Notes fields, and there are many, are manually added. I have a blog post on Notes, Notes, and More Notes.

https://ftmuser.blogspot.com/2014/04/notes-notes-notes-and-more-notes.html

for all of the blog posts on Notes:

https://ftmuser.blogspot.com/search?q=notes

____________________________________________________________
Copyright © 2019 by Cousin Russ

Reader Question: Export / Import

Another Reader Question:

When importing/exporting, the system creates a new tree.  Is this suppose to happen?

The answer is "yes" and "no", or just "it depends".

When you do a FILE, Export, and you make your choices for people and FILE Format, Yes, you will be creating a NEW FTMB (Family Tree Maker Back Up FILE) on your computer. From there, you can do a File, Restore, or send the file to some one else.

When doing a File, Merge, you are NOT creating a New File, You are given two choices, using the Import option. 1) to Amend your current, open File, or 2) Merge that the file you select, into the File you have Open. Two different things will happen.

But, the question was Importing. You get that from the Plan Workspace, New Tree (FILE).

Plan Workspace, New Tree (FILE) Import an Existing Tree

This is where you can Browse to the file you want to Import as a NEW File. You will also be asked for a Tree (FILE) Name. The difference is that you have several options of what that Existing FILE is. A Family Tree Maker Version 5 (not 2005, but very old Version 5), a PAF file, or a Legacy Family Tree File, or a GEDCOM File.

Note: a GEDCOM file will NOT include any images.

Remember that the Import option, is to create a New FILE from another Genealogy Program, or an earlier (old) version of Family Tree Maker.

Please note my use of the work FILE and not Tree, as the screen shows. To me, a TREE is an Online version of the information in the FILE the is on my computer. I have NO Trees on my computer. My computer may be dusty, but it has nothing for a Tree to grow in. It's also easier to tell the difference between information on the Computer (File) and information that is Online (Tree). But that's just me.
____________________________________________________________
Copyright © 2019 by Cousin Russ

Reader Question: What is included in the FamilySync

From a reader:

Does syncing your tree include information in the Media and Tasks tabs?

Not everything that is in your Family Tree Maker File, that you see and enter, is included in the Sync Process.

The Names, Dates, Places, Citations, and Media files are all included in the Sync Process.

There are some Media files that are NOT included when you Sync. Any Media File that you mark as Private and those Media files that come from Ancestry. For example, I have Marked this Media file as Private. I do not what this image to be in my Ancestry Member Tree.

Any FACTs that are marked Private, will also not be included in FamilySync. For example, I do not want the Address Facts that I have in my database, in my Ancestry Member Tree. So, I mark them Private.

I have Person Notes, that I am not ready to have in the Ancestry Member Tree, so I mark those notes as Private.

Research Notes / Logs, by default are marked Private and will not be put online. and the Task / To Do list are also not put online during the FamilySync Process.

Here is a link to other FamilySync articles on this blog and links to the Family Tree Maker Knowledge Base website.

____________________________________________________________
Copyright © 2019 by Cousin Russ

User Question: Merge Two Facts

I saw this question on a Facebook Group, not a Family Tree Maker group, but thought I would address it here. The user, had moved the database from one Genealogy Program to another. The question was:

Is it possible to merge 2 fact types 

[ say Address to Residence]

In FTM2017, you can right click  on any Fact, and there is a "Merge Duplicate Facts" option. That option would not work here. The Data from the Address Fact, would have to be Copied and Pasted into the Residence Fact. I am sure you all know that. 

The Reason I want to post about those two items is this:

The Residence Fact, should be used for ANY Record that claims the Location of where the Profile Resided, by Location. City, County, State, County. It's important for me, so that Place name, puts that Profile on the Map.

The Address Fact. takes that Residence Fact to the next Level. I say that, because, by Default, I have the Address Fact marked as Private. Yes, it's still on the Map, but the use of the Historical Place Name feature, resolves that Place Name, which is also important.  I have chosen, not to include any Address Fact, in the Ancestry Member Tree, since I mark that Fact as Private.

Clearly this is a user's choice. For me, I want the Address, every time I can find one, on the many records that provide it. I do NOT put that Address in the Description field, but the Place Name field and use the Historical Place Name feature.

What I have been known to do, IF that Address is in driving distance, I may go take a ride and take a picture of it. I have one photo, of where my grandmother lived in the last 1800's, in Waltham, Massachusetts. I later took my parents to that same place, so show my mother where she lived, but the house was gone. I only had the photograph to share with my mother. That photo, would be linked to a Citation, and the Citation linked to that Address Fact, marked Private.

On final thought about the Residence Fact. I have seen many users use a Census Fact. My question is always, is a Census a FACT or a RECORD ? I'll leave that answer to you.


____________________________________________________________
Copyright © 2019 by Cousin Russ

User Question: Ancestry and Media

A Question from a reader:

What can you do once Ancestry media won't process in FTM?

Easy answer: Use Help, Family Tree Maker Tech Support, and on the Right use the LIVE CHAT Support link.

https://www.mackiev.com/techsupport/ftm/livechat.html

____________________________________________________________
Copyright © 2019 by Cousin Russ

Social Security Death Index - Warning

As some of you know, I work off of Ancestry RECORD Hints, and find this works very well for me. I then will use the Web Merge feature of Family Tree Maker to get that data from the website, into my database. The REASON I do this is so that my database contains the exact information from that Record. Misspelling and all. When the Data is in my database, then I evaluate the information presented and mark the appropriate Fact as Preferred. Keep in mind, that I have already evaluated the Hint BEFORE I do the Web Merge, to make sure it is my person. This 2nd evaluation is to match this new information against the other information I already have.

Now, the reason for this blog post is to bring to your attention a problem that I have seen in a number of Records, but I will focus on ONE Record Group, the Social Security Death Index (SSDI) from Ancestry.

The issue: The Death Fact information.

I have seen this problem during the Web Merge of an SSDI Record, many times and have reported this as a Bug to Family Tree Maker. But, I wanted to see why the Web Merge was acting the way it was. The Root Cause of the problem (yes, I'll tell you in a minute), is the way that Ancestry handles this Record.

Here is a Hint, in my Ancestry Member Tree (AMT), for an Individual, for a SSDI Record:

This is a Quick Compare, in the AMT, with My information on the Right and the Record information on the Left. I only have the Year of the persons Death. The Record, in this Hint, had the Month and Date (all good) of the Death BUT is has a Death Location.

If I were to just accept that Hint, the Death Location would be Added to that Death Fact.

Here is the Issue:

If you Look at the RECORD, the Record has the Month and Year but NO Death Location. In this example, there is a Last Residence Fact, which is good, it includes the city, county, state, and Zip code. All good. BUT there is NO Death Location on that Record.

What information does the SSDI contain?

The SSDI contains the following information fields:ty number
Surname
Given Name
Date of Death
Date of Birth
Last Known Residence
Location of Last Benefit
Date and Place of Issuance

Note: the Date of Birth, nor the Date of Death items do NOT include the Location / Place. And, in the Web Merge, online or in Family Tree Maker, the Birth PLACE is not included. Only the Death Place (example in a minute)

My understand of the Last Know Residence and the Location of Last Benefit, is the last place someone lived, according to Social Security and where the Last Benefit was sent. Neither of them are noting the Place of Death.

In the Web Merge, in Family Tree Maker, as it the AMT Save Hint we see:

I will NOT accept that Place Name for the Death Fact, I must manually delete the Death Fact PLACE for an SSDI.

I caught this issue a while ago, but chose now to blog about it, when the SSDI claimed that my Grandfather Died in New Jersey. He did not, but the Last Benefit was sent to New Jersey.

My mothers SSDI claimed her last residence correctly, but the Last Benefit was sent to the same Place Name, but a different Zip Code. In this specific case, and the  reason why I enter those other Fact Names into my database, (deleting the Place of Death) is that it gave me a clue as to why my mother's estate did not include any Social Security benefits. It must have been sent to the Long Term Care facility, as part of their Contact. It IS useful information.

It is my opinion, that this is a BUG for Ancestry.com to resolve as well as Family Tree Maker to resolve.

IF the RECORD does NOT Contain the Place of Death, it should NOT be included in the AMT Merge, nor the Family Tree Maker Web Merge Feature.

____________________________________________________________
Copyright © 2019 by Cousin Russ

User Question: Blurry Media and Google+ Going away

Here is a question from a reader of this blog:

I tried attaching a media file but it came out blurry under my individual media tab. Image is clear. Is image supposed to be in two different locations since I want to be able to see image when off-line and not logged in to Ancestry?

I am new to FTM 2017 and have found your blog to be most useful. Since Google + is shutting down April 2, 2019, which blog do you recommend me joining.

The answer to your media file being blurry depends on how you obtained that image. Most of the pictures that I have are clear, some, not so much. The not so much items are ones that were handed down to me in various formats. Every time you OPEN a JPG file, and save it, it will become more compressed or blutty.

I ALWAYS keep my scanned images or digital images in their original folder on my computer. AND when I use that media file, I ALWAYS use the COPY option, when adding that image to my file.


Google+ is going away. So what. That has nothing to do with this Blog.

Now, I had a Google+ Genealogy community on Google+ and it IS going away. BUT I was able to capture all of the content from that community and created another blog with all of the content already there.

cousinrusscommunity.blogspot.com

Russ

____________________________________________________________

Copyright © 2019 by Cousin Russ

User Question: Multiple / Duplicate Birth, Marriage, Death Facts

A question from a Blog Reader:

Thank you for your Knowledge Base series. They are a great resource.

Sometimes one or more B/M/D facts have two dates and, no matter how hard 
you research the problem, you just can not figure out which is correct.

I had the problem with a birth date and kept the two Birth fact entries. 
FTM's error checking routines did not like this and kept flagging the 
two Birth entries as an error.

So, what to do? It finally hit me, the solution to duplicate facts is to 
eliminate the duplication. I kept the original Birth fact and added a 
second "Birth - ALT" fact to hold the alternate fact. The same could be 
done by creating "Death - ALT" and "Marriage - ALT" facts.

If I ever manage to resolve the conflict, all I have to do is put the 
correct date and citation(s) in "Birth" and delete "Birth - ALT."

If needed you can create a custom Report to keep track of these 
additional facts by filtering in "xxx - ALT" as "Is Not Blank."

Thought this might give you an idea for one of your video demos.

First, I am sure I have done more than one video on this topic and a number of written blog posts as well.

But, I'll try to answer your questions here.

 In this example. there are six (6) Birth Facts and three (3) Death Facts. You will note that the 3rd item down, birth fact, has 24 Citations. You might say, well that MUST be it. 

Same with the Death Fact. The 3rd from the bottom, on the right, has 24 Citations. BUT, in evaluating the Citations, I have made the determination as to which Birth and Death Fact is PREFERRED. 

Usually, the preferred fact will be the most complete set of information.

You did NOT tell me what error messages Family Tree Maker was providing. A HINT, however, IF the error you are talking about is from the Data Error Report, try selecting Preferred ONLY.

I submit to you that these are NOT Duplicate Facts !!!!! They are ALT Facts. To be "duplicate" facts ALL of the Fields in that Fact MUST be Exact. Alt Facts are see above, where a couple of Citations will give the Year only. (BMD Facts I ALWAYS use Abt. YYYY). There are a couple facts that had the full date, but not Place Name.

Bottom line: (for me)

I record what I see on the Record and Cite the source. So, when it comes time to Evaluate my data, to make that Preferred Fact determination, I can do that very quickly.

My preferred facts change all of the time, until I get what my "current thinking" is about that Fact or event.

____________________________________________________________
Copyright © 2019 by Cousin Russ

User Question: How do I batch delete unused Place Names ?

Here is the Question

I am in the midst of a major tree cleanup, moving large amounts of people into other files or deleting them. I am also doing general cleanup of the database. I am finding a lot of place names that no longer have anyone linked to them. I am assuming that the people originally attached to these places are no longer in the database. Is there a method of searching for "orphan" place names and doing a batch delete?

Quick Answer: You Can't BULK Delete Place Names without a Fact linked to that place.

My suggestion is to put the Place Names in the FLAT View, then use your down arrow on your keyboard and look in the Right Hand Panel.

I suggest that, rather than using a report, base you can Delete the Unused Place name tight here.

Yes, there is manual clean up work after you do clean up.

Also, BACK UP BEFORE you do any of this, then do a Compact and Back Up when you are done. You don't have to do that ALL at the same time. I suggest making a note as to the Letter of the alphabet that you have completed, so you can pick up where you left off.

____________________________________________________________
Copyright © 2019 by Cousin Russ

Knowledge Base - Web Search Workspace (updated)

Web Search Workspace

• Using FamilySearch in FTM 2017 for Windows (31 Aug 2017)
• Ignoring Web Search Results in FTM 2017 for Windows (01 Sep 2017)
• Merging Web Search Results into a Tree in FTM 2017 for Windows (01 Sep 2017)
• Saving or Printing Images in Web Search in FTM 2017 (01 Sep 2017)
• Starting a Web Search in FTM 2017 for Windows (01 Sep 2017)
• Empty Ancestry Search Results and Missing Categories in FTM 2017 Web Search [Fixed in 23.2] (28 Sep 2018)
• Blank “Edit Search” Window in FTM 2017 Web Search (01 Oct 2018)
• Errors from Ancestry Hints or Web Search Results (11 Nov 2018)
• Search Result Detail Issue in FTM 2017 23.2 (12 Nov 2018)
• Troubleshooting Chromium Embedded Framework Issues in FTM 2017 for Windows (14 Dec 2018) [ NEW ]

From this blog:

• Web Search Workspace

____________________________________________________________
Copyright © 2019 by Cousin Russ

Knowledge Base - General Program Articles (update)

There are a number of articles of general nature that will be posted here:

• NEW TREE SAFETY FEATURES (FTM 2017) (23 Jun 2017)
• Resolving Performance Issues in Family Tree Maker 2017 (21 Sep 2017)
• Moving a Tree from an Earlier Version to FTM 2017 for Windows (03 Oct 2017)
• Purchasing FTM 2017 (07 Dec 2017)
• Troubleshooting Installation for FTM for Windows (09 Jan 2018)
• Saving a Crash Log for FTM 2017 for Windows (09 Jan 2018)
• Uninstalling FTM for Windows (17 Jan 2018)
• Finding Family Tree Maker Files in Windows (25 Jan 2018)
• System Requirements for FTM 2017 (14 Feb 2018)
• Fixing Display Issues in FTM for Windows (13 Mar 2018
• Importing an Existing File in FTM for Windows (05 Apr 2018)
• Generating and Sending a Sync Error Report for FTM 2017 for Windows (09 May 2018)
• Guide to Updating the FTM 2014.1 USB Drive to FTM 2017 (09 May 2018)
• Ancestry Services in Older Editions (14 May 2018)
• How to pick up your copy of FTM 2017 (01 Jun 2018)
• Manually Uninstalling FTM 2017 for Windows (02 Jun 2018)
• Keyboard Shortcuts in FTM 2017 for Windows (12 Sep 2017)
• Moving a Tree from FTM 2017 for Windows to FTM 2017 for Mac (04 Oct 2017)
• Getting a Replacement Download for FTM 2017 (09 Oct 2018)
• Free Update 23.1 for FTM 2017 (10 Nov 2018)
• Installing Family Tree Maker 2017 for Mac (06 Jun 2018)
• Installing Family Tree Maker 2017 for Windows (06 Jun 2018)
• “Format the disk” warning when inserting the FTM USB Drive (10 Jun 2018)
• Workspaces (Tabs) in FTM 2017 for Windows (12 Jun 2018)
• Opening Old and Unsupported Files in FTM 2008-2017 for Windows (16 Jun 2018)
• Comparing FTM and Ancestry Trees when using FamilySync (29 Jun 2018)
• FTM 2017 for Windows Crashes or Closes Unexpectedly (02 Jul 2018)
• Resetting Program Settings to Default in FTM 2017 for Windows (12 Jul 2018)
• Troubleshooting Connectivity Issues in FTM 2017 for Windows (03 Aug 2018)
• Troubleshooting Sync in FTM 2017 for Windows (28 Aug 2018)
• HOW TO COMPACT AND BACK UP A LINKED TREE (28 Sep 2018)
• What's New in Family Tree Maker 2017? (04 Oct 2018)
• FAMILY TREE MAKER 2017 FAQ (08 Nov 2018)

____________________________________________________________
Copyright © 2019 by Cousin Russ

Knowledge Base - FTM2017 for the Mac (update)

Here are some specific Mac Knowledge Base articles:

• Using Color Coding in FTM 2017 for Mac (04 Dec 2017)
• Uploading a tree from FTM 2017 for Mac to Ancestry (01 Dec 2017)
• Moving a tree from FTM 2014 for Windows to FTM 2017 for Mac (01 Dec 2017)
• Downloading a tree from Ancestry to FTM 2017 for Mac (01 Dec 2017)
• Restoring a Tree from a Backup File in Family Tree Maker 2017 for Mac (27 Nov 2017)
• Compacting a File in Family Tree Maker 2017 for Mac (29 Dec 2017)
• Using the Find Missing Media tool in Family Tree Maker for Mac (29 Dec 2017)
• Checking Mac OS X Version and Processor Information (17 Jan 2018)
• Uninstalling FTM for Mac (17 Jan 2018)
• Troubleshooting Installation for FTM for Mac (13 Feb 2018)
• Guide to Replacing the FTM 2017 Mac Installer on the USB (06 Mar 2018)
• Moving a tree from earlier versions to FTM 2017 for Mac (27 Mar 2918)
• Generating and Sending a Sync Error Report for FTM 2017 for Mac (09 May 2018)
• Guide to Updating the FTM 3.1 USB Drive to FTM 2017 (09 May 2018)
• Merging Duplicate Individuals in FTM 1-3 and 2017 for Mac (14 Jun 2018)
• Opening Old and Unsupported Files in FTM 2017 for Mac (16 Jun 2018)
• Backing Up a File in FTM 2017 for Mac (22 Jun 2018)
• Troubleshooting Sync in FTM 2017 for Mac (28 Aug 2018)
• FTM 2017 for Mac Crashes or Closes Unexpectedly (05 Sep 2018)
• Troubleshooting Connectivity Issues in FTM 2017 for Mac (14 Sep 2018)
• Resetting Program Settings to Default in FTM 2017 for Mac (14 Sep 2018)
• Sync Issue - Media Not Uploading from FTM 2017 for Mac [Fixed in 23.2] (28 Sep 2018)
• Ancestry Login Issue - FTM 2017 for Mac [Fixed in 23.2] (01 Oct 2018)

____________________________________________________________
Copyright © 2019 by Cousin Russ

Knowledge Base - General Program Articles (update)

There are a number of articles of general nature that will be posted here:

• NEW TREE SAFETY FEATURES (FTM 2017) (23 Jun 2017)
• Resolving Performance Issues in Family Tree Maker 2017 (21 Sep 2017)
• Moving a Tree from an Earlier Version to FTM 2017 for Windows (03 Oct 2017)
• Purchasing FTM 2017 (07 Dec 2017)
• Troubleshooting Installation for FTM for Windows (09 Jan 2018)
• Saving a Crash Log for FTM 2017 for Windows (09 Jan 2018)
• Uninstalling FTM for Windows (17 Jan 2018)
• Finding Family Tree Maker Files in Windows (25 Jan 2018)
• System Requirements for FTM 2017 (14 Feb 2018)
• Fixing Display Issues in FTM for Windows (13 Mar 2018
• Importing an Existing File in FTM for Windows (05 Apr 2018)
• Generating and Sending a Sync Error Report for FTM 2017 for Windows (09 May 2018)
• Guide to Updating the FTM 2014.1 USB Drive to FTM 2017 (09 May 2018)
• Ancestry Services in Older Editions (14 May 2018)
• How to pick up your copy of FTM 2017 (01 Jun 2018)
• Manually Uninstalling FTM 2017 for Windows (02 Jun 2018)
• Keyboard Shortcuts in FTM 2017 for Windows (12 Sep 2017)
• Moving a Tree from FTM 2017 for Windows to FTM 2017 for Mac (04 Oct 2017)
• Getting a Replacement Download for FTM 2017 (09 Oct 2018)
• Free Update 23.1 for FTM 2017 (10 Nov 2018)
• Installing Family Tree Maker 2017 for Mac (06 Jun 2018)
• Installing Family Tree Maker 2017 for Windows (06 Jun 2018)
• “Format the disk” warning when inserting the FTM USB Drive (10 Jun 2018)
• Workspaces (Tabs) in FTM 2017 for Windows (12 Jun 2018)
• Opening Old and Unsupported Files in FTM 2008-2017 for Windows (16 Jun 2018)
• Comparing FTM and Ancestry Trees when using FamilySync (29 Jun 2018)
• FTM 2017 for Windows Crashes or Closes Unexpectedly (02 Jul 2018)
• Resetting Program Settings to Default in FTM 2017 for Windows (12 Jul 2018)
• Troubleshooting Connectivity Issues in FTM 2017 for Windows (03 Aug 2018)
• Troubleshooting Sync in FTM 2017 for Windows (28 Aug 2018)

____________________________________________________________
Copyright © 2019 by Cousin Russ

Knowledge Base - FTM2017 for the Mac (update)

Here are some specific Mac Knowledge Base articles:

• Using Color Coding in FTM 2017 for Mac (04 Dec 2017)
• Uploading a tree from FTM 2017 for Mac to Ancestry (01 Dec 2017)
• Moving a tree from FTM 2014 for Windows to FTM 2017 for Mac (01 Dec 2017)
• Downloading a tree from Ancestry to FTM 2017 for Mac (01 Dec 2017)
• Restoring a Tree from a Backup File in Family Tree Maker 2017 for Mac (27 Nov 2017)
• Compacting a File in Family Tree Maker 2017 for Mac (29 Dec 2017)
• Using the Find Missing Media tool in Family Tree Maker for Mac (29 Dec 2017)
• Checking Mac OS X Version and Processor Information (17 Jan 2018)
• Uninstalling FTM for Mac (17 Jan 2018)
• Troubleshooting Installation for FTM for Mac (13 Feb 2018)
• Guide to Replacing the FTM 2017 Mac Installer on the USB (06 Mar 2018)
• Moving a tree from earlier versions to FTM 2017 for Mac (27 Mar 2918)
• Generating and Sending a Sync Error Report for FTM 2017 for Mac (09 May 2018)
• Guide to Updating the FTM 3.1 USB Drive to FTM 2017 (09 May 2018)
• Merging Duplicate Individuals in FTM 1-3 and 2017 for Mac (14 Jun 2018)
• Opening Old and Unsupported Files in FTM 2017 for Mac (16 Jun 2018)
• Backing Up a File in FTM 2017 for Mac (22 Jun 2018)
• Troubleshooting Sync in FTM 2017 for Mac (28 Aug 2018)
• FTM 2017 for Mac Crashes or Closes Unexpectedly (05 Sep 2018)
• Troubleshooting Connectivity Issues in FTM 2017 for Mac (14 Sep 2018)

____________________________________________________________
Copyright © 2019 by Cousin Russ