Just downloaded V5 and installed fine. Loaded my main project and was told about 20-30 errors in file which were flagged as 'info only'. Had a good look at the file but couldn't see any particular problems. Reloaded and all now seems as normal. The error message apparently refers to errors in the file which have been fixed but, as the file has been in use in V4 for some time I'm not sure why these should come to light now. Not complaining as all seems ok but would be interested to hear if anybody else has the same issue when upgrading.
ID:6035
* Version 5 - Strange 1st time load
- Jane
- Site Admin
- Posts: 8441
- Joined: 01 Nov 2002 15:00
- Family Historian: V7
- Location: Somerset, England
- Contact:
Version 5 - Strange 1st time load
When ever you install a new version of FH, it does a validate over the file, so if you did not tidy up any problems when you installed V4 they will be flagged again in V5.
-
nsw
Version 5 - Strange 1st time load
FH v5 looks at the GEDCOM file and if for example it has:
0 HEAD
1 SOUR FAMILY_HISTORIAN
2 VERS 4.0
it then warns you about any uncategorised data. Once you've saved the file it will change it to:
0 HEAD
1 SOUR FAMILY_HISTORIAN
2 VERS 5.0
and then it doesn't warn you in the future (presumably until version 6!) unless you validate manually.
0 HEAD
1 SOUR FAMILY_HISTORIAN
2 VERS 4.0
it then warns you about any uncategorised data. Once you've saved the file it will change it to:
0 HEAD
1 SOUR FAMILY_HISTORIAN
2 VERS 5.0
and then it doesn't warn you in the future (presumably until version 6!) unless you validate manually.
Version 5 - Strange 1st time load
It might be a bit more complicated than that. I loaded v.4, validated - no errors. Upgraded to v.5 - 3 errors on initial load automatically corrected - validated subsequently - no errors. Closed v.5 without making my project the default and reloaded - 3 errors as before. Did this twice more with the same result before saving project as default, then v.5 loads fine.
The errors were all field format errors where 2 TYPE was replaced by 2 NOTE in a 1 ASSO branch.
The errors were all field format errors where 2 TYPE was replaced by 2 NOTE in a 1 ASSO branch.
- tatewise
- Megastar
- Posts: 27084
- Joined: 25 May 2010 11:00
- Family Historian: V7
- Location: Torbay, Devon, UK
- Contact:
Version 5 - Strange 1st time load
You will keep getting the same validation errors until you Save, because only then is the GEDCOM file updated as Nick explained above.
Setting the Project Default was probably just coincidental.
Setting the Project Default was probably just coincidental.