I have just been entering a couple of Marriage details using Ancestral sources (v5.2 64 bit). I then closed AS and returned to FH (v6.2.6) and did the normal update.
For the first time ever, I received an error message
I was also recommended to validate the file which I did and it reported no errors.Family Historian Exception Report - Tuesday 29 May 2018
=========================================================
Lines marked "EXCLUDED:" indicate data which has not
been loaded, and explain why it wasn't loaded.
Indented lines marked "EXCLUDED BRANCH LINE:" indicate
data lines which are not necessarily invalid in
themselves but which have had to be excluded as a
consequence of excluding other lines.
Lines marked "INFO ONLY:" indicate data that has
been successfully loaded, but where special action
was needed to load it (e.g. GEDCOM errors detected
and automatically corrected by Family Historian).
---------------------------------------------------------
Record Type=Individual. Gedcom Id=I828. Record Number=800.
l.12184 - EXCLUDED: invalid line : "(Retired)"
l.12185 - EXCLUDED BRANCH LINE: : "2 DATE 12 SEP 1963"
l.12186 - EXCLUDED BRANCH LINE: : "2 SOUR @S157@"
l.12187 - EXCLUDED BRANCH LINE: : "3 QUAY 3"
---------------------------------------------------------
The numeric portion of Gedcom Ids have been retained as Record Ids. Use these to match entries to records.
I looked at the Forum for "EXCLUDED BRANCH LINE", and got 17 hits, all of which I've read, but while they are similar, they are not the same as my report.
search.php?st=0&sk=t&sd=d&sr=posts&keyw ... RANCH+LINE
The line 12185 is clearly from the last Marriage details that I input. But other than that I can see little difference in this record from others I have input that might suggest why I got an error, on this record.
I have closed and re-opened the file, and no error is now reported. I also have re-booted the PC as well just in case it clears any gremlins. (I'm running Win 10 which is kept up-to-date, and good virus software)
I have plenty of backups if I need to revert to a previous version, but presumably I would potentially just generate the same error when I came to input this record.
Any suggestions as to what the issue may have been would be appreciated.
Thanks
Colin