* Exception Report Question with FTM import

[McHooty]

Hi
Just a question about the Exception Report generated when I load my FTM Gedcom file into FH 7 (Trial).

I have thousands of 'INFO ONLY: Detected & fixed invalid use of EVEN (event) tag:' entries.
The majority relate to text that is present in the 'Description' field (as in Date / Place / Description) of my FTM Fact.

The question is - Is this because I should have originally entered the information in the 'Notes' field, or is it down to something else such as my use of Custom Facts ?
The reason I have for doing it this way is so that the information is easily visible without having to look into the fact details.

Thanks in advance

[tatewise]

It is related to the use of Custom Facts.

I think FTM 2019 supports the GEDCOM 5.5.1 specification, which FH v7.0 adheres to very closely.
Custom Events should use the EVEN tag but not allow a Description value.
Custom Attributes should use the FACT tag and allow a Description value.
However, I suspect FTM is like many other products and allows Custom Events to have a Description value.
That is what the Exception Report is complaining about and has fixed.
I think the fix converts the EVEN tag Event to a FACT tag Attribute.
Please confirm that assumption is correct, i.e. Are your Custom Events becoming Custom Attributes in FH?
Every Standard and Custom Attribute has a descriptive value box in the Facts tab that Events do not have.

Your options are either to change the FTM Custom Events into Custom Attributes, or just live with the Exception Reports.
Assuming you are migrating permanently to FH then the latter is the better option.

[McHooty]

Hi Mike

As confirmation my FTM Custom Facts/Events are being converted to Custom Attributes in Family Historian.
I will be migrating to Family Historian so will accept that as you suggest.

You mention FTM 2019 supporting Gedcom 5.5.1. I did ask the question earlier whether importing from FTM 2017 or FTM 2019 would make any difference and Jane suggested that it wouldn't. Do you know something different ? (I do have the 2019 version but don't use it. I suppose the ideal route would be to load my data into that and then export the Gedcom for FH to use).

Apologies for going off subject.

[tatewise]

I don't know whether FTM 2017 differs from FTM 2019 regarding the GEDCOM version supported.
Unfortunately, I don't have either FTM 2017 or FTM 2019 (too expensive), but maybe another user can advise.

Since the FH Fact import seems to work to your satisfaction, then just ignore the Exception INFO ONLY reports.
However, do take note of the other reports.
See Importing to Family Historian under Import from Family Tree Maker (FTM) and follow all the advice.
Does the Export Output Format option shown there as GEDCOM 5.5 agree with the options you have available?
e.g. Is GEDCOM 5.5.1 available?

Certainly, try FTM 2019 as an experiment, check its Export Output Format options.
A later version of a product is likely to fix some issues in earlier versions so may produce a better GEDCOM file.

[McHooty]

Just an update.
Both my copy of FTM 2017 and 2019 only show Gedcom as an export option (without a version number).
However, after a bit of research it appears that FTM complied with Gedcom 5.5.1 from version 2017, and I assume 2019.
Using identical data the size of the .ged files generated varies by 178kb between versions. 2019 is the larger, but this could be because the FTM file structure changed between the two.
The FH Exception Reports produced when loading the two .ged files as new projects are identical in size and output.
Also, the number of media links is the same.
All of which proves absolutely nothing