My rather large Family Tree when imported into FH4 generates an exception report when loading. The exception report states that some of the sources are invalid (exceeds max.) and won't load them. They worked fine under FH3.x.
I'm puzzled and the report doesn't help me much in understanding the problem. I'm regretting the upgrade already.[cry]
ID:3717
* Exception Report importing a V3 GEDCOM into V4
- Jane
- Site Admin
- Posts: 8442
- Joined: 01 Nov 2002 15:00
- Family Historian: V7
- Location: Somerset, England
- Contact:
Exception Report importing a V3 GEDCOM into V4
This is a correction to the limits on the number of text fields on a source, which was allowed incorrectly on V3.
John Axtell has done a work around fix for this. Which he has added as a download, but the link is broken at the moment, hopefully it will be back.
Many people have found that the excluded data was simply repeats of other text from merges. It's not excluded the whole source simply the extra text.
John Axtell has done a work around fix for this. Which he has added as a download, but the link is broken at the moment, hopefully it will be back.
Many people have found that the excluded data was simply repeats of other text from merges. It's not excluded the whole source simply the extra text.
Exception Report importing a V3 GEDCOM into V4
Thanks Jane
Does that mean that the 'invalid branch' lines indented under each exclusion are the duplicated lines?
It seems strange for a piece of software which boasts strong error checking should itself create such an error - without it having been 'bug-fixed'. I've used only FH 3.x and Gedcom Census for my research.
Does that mean that the 'invalid branch' lines indented under each exclusion are the duplicated lines?
It seems strange for a piece of software which boasts strong error checking should itself create such an error - without it having been 'bug-fixed'. I've used only FH 3.x and Gedcom Census for my research.
- Jane
- Site Admin
- Posts: 8442
- Joined: 01 Nov 2002 15:00
- Family Historian: V7
- Location: Somerset, England
- Contact:
Exception Report importing a V3 GEDCOM into V4
V4 fixed an outstanding problem in V3 which allowed the other lines to be added in error.