1. Multiple: (V5) If you have more than 13 facts, you are shown a facts page with 13 visible facts and a scroll bar to view the rest.  The PgUp and PgDn keys do not work on this page.
2. Marriage ending status: (V6) Marriage ending status fact will not print in reports. 

1. Once a person has had a title entered for them (More About, Lineage); the "mark" on the family page indicating the presence of notes  becomes indelible. Deleting the title will not erase it.
2. "Marked for notes" Suppose there is a non-natural relationship, such as denoting that a child is step-child of one parent. The parent in question is later found to be incorrect. The person is deleted or detached from the family page. The child remains tagged as "notes present". Later the actual natural father is added to the page. Whether simply entered from scratch or by attach spouse, there is no request to correct the relationship, which is 'remembered' as step. You will have to notice this and reset the relationship. Once this is fixed, the child will no longer be marked for notes. 

3. Family Page Status Bar: This is the bar at the bottom of the Family Page. It will display the names of the parents of the selected individual, for example. Except as follows:
1. Bring up a family page of someone who has parents listed.
2. Select the husband or wife who has parents using the cursor keys
3. Observe the parent names in the Status Bar. 
4. Click on any of the Menu Bar items, such as People
5. Observe the Status Bar says, rather redundantly, "Display the People Menu" 
6. Click on the individual of step 2
7. Observe that: 
• The menu goes away
• The highlight on the name goes away
• The Status Bar still says: "Display the People Menu"
The only way to restore the proper Status Bar display is to click on any field but the one that was active just prior to the Menu Bar item. This same effect obtains with any of the Menu Bar items and the two tree items on the Toolbar.
4. Children list: Scroll children to any one after #4, click her "More" button to enter details. Click "Parents of" to return, but the scrolling point in the children display has been lost, reverting to 1-4. The analogous situation with spouses, where it is seldom needed, works properly – Why not children? 

parent names
 

Status Bar

Observe

1. Fields: A list is provided of fields that may be searched, including "Any and all text fields." This is misleading, as some text fields are excluded, such as Title (e.g. "Doctor"). In fact, there is no way to search the Title field.
2. Strings: A key aspect of this search has never been revealed: Find treats the string that you enter as multiple strings, separated by blanks or special characters, and uses these as individual search arguments connected by the logical .AND. operation. Not knowing this very important fact, the Find seems to work in very bizarre fashion indeed! 
3. Search dates: permits use of the "special dates", like "child", but does not permit search for the prefix "WFT". (One might want to find all these, perhaps to remove them.)
4. Inconsistencies: Different fields are searched in different ways. Two strings entered as a search argument for "Any and all text fields" will match those strings (using the .AND. logical connective) in the name field if they appear in any order. However a match in the Birthplace field (or death-, or marriage-place) must find those strings in the same order as entered in the search argument. E.g. a man with the name "New York" with a wife born in "New York", entering "new york" in the Search For slot will find both, but "york new" will only find the husband.

very bizarre

5. Search dates: Search for individuals with a specific birthdate, say "28JUN1635" will find all those individuals whose birthdates were entered as 
1. open or closed ranges that span the sought date (e.g. "1622-1650", "before 1900"), or 
2. imprecise and close to that date (e.g. "ca 1640"), or
3. that exact date. 
Users become quite upset by this behavior, but would be equally upset if those imprecise dates were NOT found! FTM could really use an option on the Find Individual that would modify date searches to be exact, so that "28JUN1635" would only find that exact date, and "Abt. 1635" would only find dates entered as "Abt. 1635" (but not "Abt. 1636").
6. Highlighting finds: Find in "Birth location" highlights the found birth location. Find in "Marriage location" highlights one of the names instead of the marriage location.

1. White lines in images (V6): A problem affecting the quality of images in version 6 was related and debated in the forum for many days. Some brilliant sleuthing by Martin Goebel pinned down the specific causes.

1. Unnamed individuals, denoted by "\\", appear in the index (and in several reports) as "<Unnamed>". Click Index (or F2), and entry of a character, e.g. "A", will position the index to the first surname beginning with that character. Entering "<" does not position the index to the first "<Unnamed>" — unless this string, "<Unnamed>", had been explicitly used as a surname in a name or a/k/a field. In this case, the index will be positioned at the first of these explicit entries, the implicit ones (denoted by "\\") being ignored.
2. Abbreviation: (V6) If sorted by married name, a woman's middle name will be dropped. John Doe's wife Mary Elizabeth Smith appears in the index as "Doe, Mary Smith." 
3. Order: (V6) Names are displayed in incorrect order with option to list women by married name. Ann Jones married to Joe Smith will be listed before unmarried Ann Smith:
Smith, Ann Jones
Smith, Ann

1. There are buttons to includeAncestors> and Descendants>, but no corresponding buttons to exclude groups by the same criteria.  One must find those options under the <Find button.

1. This mini-dialog is presented when FTM detects an apparent duplicate individual being entered. Without an opportunity to review the associated data with both individuals, it is rarely the case that "Yes" can safely be answered to this question.  Answering "Yes" will bring up the usual Merge comparison, which includes a Cancel button. The Buttons on the "Is this child..." dialog should be labeled "View details", and "No".

1. Terminology: The checkbox labeled "Mr./Mrs." should be labeled "Titles", as this is the term for what is controlled by this option. It is better to label the option with a category name than with an example (Mr./Mrs.).

1. Undo (CTL-Z): Recovers incorrect field content.
1. On family page, select/highlight the father
2. F6 to navigate to first offspring (must be male)
3. "Accidentally" type any character over offspring's name
4. Immediately, use CTL-Z (or Edit | Undo)
5. The recovered string will be the father's name (or sometimes null), not the overtyped offspring.
There are a number of interesting variations, with equally injurious results. 
2. Function Keys: Some have complained of the inverted positioning of the F4 (wife's parents) and F5 (husband's parents) keys relative to the placement of their referents on the Family Page (husband first).

1. Navigation: Up- and Down-arrows will not move the cursor into or out of the Medical Information field.

1. Merge Individuals Dialog: The version 5 dialog mentions buttons to push to keep certain items. There are no buttons. 
2. Merge Files Report: The report is shown in a ridiculously small window, with no way to expand it. 
3. Ordering: Following a Merge (e.g. by importing from files, or selecting People/Merge…) children or spouses may not appear in date order, even if previously sorted.

1. The method for rearranging (other than sort by date) an offspring list is arcane, and instructions are imprecise, leading to probable error. Instructions specify to orient on the desired slot in the list, which will lead to inconsistent results. Better to orient on individual before whom the target child will be moved.

1. Labels: Changing the words of the last column do not always have the expected effect. For example, changing "in:" (the last one), changes its appearance in the Family Group Sheets, but not in the Genealogy Reports.

1. Various activities display a progress bar with a big "Cancel" button. The program is annoyingly slow in recognizing when this button has been pushed. Sometimes, it fails to notice at all.

1. Position: The dialog box sometimes covers the spot in the text where the word is located, so you lose the contextual reference sometimes needed to decide whether the word is correct or not.
2. Word length: Spell Check should ignore words of length "1", but does not, leading to needless dithering over initials in names and such, complete with a suggested a list of other single letters as "correct" spellings.
3. Quotes: Spell Check doesn't like single-quoted strings 'like this'. It accepts the leading quote, but always has a problem with the last word in the quote.