That message is an error in the formatting template caused by unexpected GEDCOM data in your file. A “Browser Style" should expect anything, but sometimes hard to program for all possible things.
I would have to see the data to be sure, but I see from screen shot that your file as non-standard GEDCOM tags such as FATH, MOTH, and ADDR (or address). The first two are not part of GEDCOM and I think made up by Family Tree Maker (some versions of Family Tree Maker exported very bad GEDCOM files). An ADDR for address is part of GEDCOM, but it cannot be at the root level. To look for it are the wrong level:
1. Select the “LARRY NELSON” in the index window.
2. Choose “Show GEDCOM Source” menu command (if it is not already showing in your index window). This will show the raw GEDCOM data for Larry Nelson in lower right part of the index window.
3. I expect you will find the following data in that GEDCOM data
1 ADDR 2417 S Kathy Lane
2 CONT Bartonville, IL 61607
but that is a GEDCOM error. ADDR tags are not allowed at level 1. All residences should have their address within a residence event (RESI). Valid GEDCOM data for an address would look like
1 RESI
2 DATE 2020
2 PLAC Illinois, USA
2 ADDR 2417 S Kathy Lane
3 CONT Bartonville, IL 61607
The DATE and PLAC give data and place for an individual's residence. The ADDR lines are moved to level 2 and give more details.
But, it looks like that bad ADDR was formatted correctly as it appears in the your screen shot. The error message says a problem in tg=he “Event Editing” template and that was probably trying to format some other bad data created by Family Tree Maker that came after the ADDR lines. Here are some fixes:
1. First, I should update the “Default Format” to work even with such bad Family Tree Maker files. I can fix it if I know what bad GEDCOM is causing the problem. My guess is that Family Tree Maker put an event meant for a family record in an individual record. So, it looks loike valid GEDCOM, but is in the wrong type of record. I would know for sure if you sent me the raw GEDCOM data. I don’t think I need an entire file just repeat steps 1 and 2 above. Then click in the raw GEDCOM data section, select all, and email to me (you can send privately to
jo...@geditcom.com). You can remove any personal details if needed, but don’t delete the bad GEDCOM. It is something after the 1 ADDR line described above.
2.A coding hack you can do at home to eliminate the error is:
a. Hold down option key and select “Browser Styles->Default Format” from the Extensions menu. This will open that style for editing the GEDitCOM Editor.
b. Expand the “Record Editing” section and click on “INDI_Other Record Editing” in the list on the left. That template will appear on the right.
c. Right near the beginning, add the line #first=“no” so that template starts like this (the first two lines are already there)
GoSub INDIPanes,"Other"
GoSub ResetTabs,0
#first=“no"
d. Choose “Save and Run” command
e. Go back to GEDitCOM II, open “Larry Nelson”, and click on “Other” tab. That error cannot occur (because #first is now defined), but because the record has bad GEDCOM data, the output may not look great (but, at least it will be there and the error message should go away).
This option #2 might be solution I add to the “Default Format.” Once I see the bad GEDCOM data, however, another solution might be more appropriate.
Regards,
John Nairn