* Gedcom Export Plug-in for Gedstar Pro

[David Potter]

One for Mike if I may please...

I have run the Export Gedcom File plugin (after updating to the latest version > 5.1), with the target being Gedstar Pro for Android I received an error, see attached image.
I then tried resetting the plugin to defaults but the error persists. If I click okay on the error message the process stops altogether. Any ideas on how to fix very welcome.

Merry Christmas All

[tatewise]

Just to be clear ...
It is not the ExportGedcom File plugin that is reporting an error but the GedStar Pro Windows conversion application.
It seems that there is a problem with line #127634 in the Export folder 1_AS GSP UTF8.ged GEDCOM file.

Could you open that GEDCOM file in a plain text editor such as NotePad and post the lines around line #127634.
Then I'll have a better clue about the cause of the problem.

[David Potter]

Hi Mike

Yes correction it is the Gedstar Pro program > Convert Database button that leads to this problem.

Here is an extract of data either side of the failing data line, the line in BOLD is the failing line number 127634.

2 NOTE Witness Role: Beneficiary [I1762] Frances MARTIN
3 CONT Witness Role: Second Wife.
3 CONT Witness Role: Executor and Beneficiary [I1870] James NIND
3 CONT Witness Role: Uncle.
3 CONT Witness Role: Executor and Beneficiary [I1400] John NIND
3 CONT Witness Role: Brother.
3 CONT Witness Role: Beneficiary [I1866] Mary NIND
3 CONT Witness Role: Believed to be a Child from Isaac's first Marriage.
3 CONT Witness Role: Beneficiary [I1867] William NIND
3 CONT Witness Role: Believed to be a Child from Isaac's first Marriage.
3 CONT Witness Role: Beneficiary [I1868] Robert NIND
3 CONT Witness Role: Believed to be a Child from Isaac's first Marriage.
3 CONT Witness Role: Beneficiary [I1863] John NIND
3 CONT Witness Role: Believed to be a Child from Isaac's second Marriage.
3 CONT Witness Role: Beneficiary [I1864] James NIND
3 CONT Witness Role: Believed to be a Child from Isaac's second Marriage.
3 CONT Witness Role: Beneficiary [I1865] Benjamin NIND
3 CONT Witness Role: Believed to be a Child from Isaac's second Marriage.
1 OCCU Yeoman
2 DATE 20 Jun 1762
2 SOUR @S1326@
3 QUAY 2
1 RESI
2 DATE 20 Jun 1762
2 PLAC Walton Cardiff, Nr Tewkesbury, Gloucestershire, England
3 NOTE Cited Source: [S1684] [unknown record]
2 SOUR @S1326@
3 QUAY 2
1 RESI
2 DATE Bef 13 Aug 1763
2 PLAC Walton Cardiff, Nr Tewkesbury, Gloucestershire, England
3 NOTE Cited Source: [S1684] [unknown record]
2 SOUR @S1322@
3 DATA
4 DATE 13 Aug 1763
3 QUAY 2
1 DEAT
2 DATE Bef 13 Aug 1763
2 PLAC Walton Cardiff, Nr Tewkesbury, Gloucestershire, England
3 NOTE Cited Source: [S1684] [unknown record]
2 SOUR @S1322@
3 DATA
4 DATE 13 Aug 1763
3 QUAY 2
2 NOTE Individual's Age: 49y
3 CONT Fact Flags: Preferred
1 BURI
2 DATE 13 Aug 1763
2 PLAC Ashchurch, Nr Tewkesbury, Gloucestershire, England

[tatewise]

The error message suggests that the faulty GEDCOM line has no leading digit level number.
But there is nothing wrong with 1 RESI
Are you sure that is really line #127634?

You could try opening that 1_AS GSP UTF8.ged GEDCOM file using FH which gives better error messages.
If a leading level digit really is missing then the Exception Report will say something like:
Record Type=Individual. Gedcom Id=I6. Record Number=1.
l.113 - EXCLUDED: invalid line : "RESI"
That refers to Individual record Id [6] line number 113

( Don't try and use that GEDCOM with the GSP Pro converter after using FH as it will probably have been changed by FH. )

Otherwise, if you don't mind, can you attach the GEDCOM file as an ATTACHMENT so I can examine it to see what is wrong.
However, it might be too large and need to be put in a ZIP file or split into parts.

[AdrianBruce]

Is it possible that there is a leading space or something in front of the 1 in "1 RESI"? It really doesn't look like it has the same relationship to the "3" above as further down...

[David Potter]

Hi Mike
Thanks for looking into this. Attached is a screen shot confirming Notepad stating that the line I highlighted is in fact line 127634.

I'll do as you suggest and open the file and view the logs using FH. Back soon with results.

@Adrian - thanks Adrian, checked and confirmed there is only one space in that data.

[David Potter]

Mike I opened the Exported Gedcom file using FH and viewed the Log Files. There are errors but none that reference line 127634.

Can I please send you the Gedcom file? Which one would you prefer, the Gedcom file for the Project. Or the Gedcom file created via the Export Gedcom plugin?

Thanks again for your help.

[tatewise]

As an experiment, I've run a Gedstar Pro conversion on a GSP GEDCOM file with a deliberate missing leading level number.
It reported exactly the faulty line number with exactly the same message as in your screenshot.
So are you sure the GEDCOM file inspected in Notepad with no problem is the same as that being converted by Gedstar Pro?
I've found that Gedstar Pro can hang on to the wrong Database File Name, so double-check the Select Database... option.

I suspect that sending me the GEDCOM file you are inspecting in Notepad and loading into FH with no appropriate errors will not reveal any more to me than it does to you. So I suspect the problem lies elsewhere.

If you still cannot resolve the problem then it might be best to send the original Project GEDCOM file so I can recreate the GSP GEDCOM from scratch. If the GEDCOM is too big to attach here then Contact me by Email via my profile.

[David Potter]

Hi Mike.
As an aside I also checked that the Gedstar Pro conversion also handled the FH Sample Project okay and it did so without error.

I'll make another test now checking the source Gedcom is the right one going into Gedstar Pro.

Thanks Mike.

[David Potter]

Hi Mike
It is possible Gedstar was referencing the wrong target folder for the Gedcom file previously.
I have run a new test and it it now reports a different error line number. I have attached the screen shot of the Gedstar error and the FH Log File showing the list of encountered errors in the gedcom file when it is opened as a standalone Gedcom file. Strangely there are no Log Files present in the Log File window in FH when looking at the exported gedcom opened in FH as a standalone gedcom.

Here are the steps I followed...

Clear the Target Folder of any Gedcom files.
Run the Export Gedcom Plugin to create a new Gedcom and place it in the Target Folder.
Run the Gedstar conversion after firstly making sure it is pointing to the correct folder and Gedcom file target.
Capture the screen shot of the Gedstar Error message which now detects line 127236 as being in error.
Opened the same Gedcom using FH as a standalone Gedcom and agreed for error checking to be done.
The first error in the FH Log file is indeed 127236.

[David Potter]

Hi Mike
I tried to send you an email via your profile and hoping to attach my zipped master gedcom file. I wasn't able to attach anything before it was sent. Sorry.

[David Potter]

Hi Mike
A few observations:

When running the Export Gedcom Plugin for Gedstar Pro, With the 'Desktop' selected as the Export Folder.
The Empty Export Folder option button causes the Plugin to freeze and then needs to be force closed. Can you reproduce that?

I copied my Master Project Gedcom file from the FH Project Folder to the Desktop. I then ran the Gedstar Pro conversion directly from that Folder/File. No errors were reported and the conversion completed successfully.

[tatewise]

OK, so now the error and line number are consistent in both Gedstar Pro and FH and the Log File shows an _FMT tag with no leading level digit.
Standalone GEDCOM cannot save Log Files as there is no Project folder to save them in.

I will investigate the Desktop as Export folder problem.
Gedstar Pro offers good GEDCOM support so it is not surprising the FH GEDCOM raises no errors, but you may find that some data does not appear in Gedstar Pro on your Android device as well as it will after using the plugin.

You cannot add attachments to FHUG Emails, but I have replied and you can reply to me with the GEDCOM attached.

[David Potter]

Morning Mike
I have now sent you my Master Project Gedcom file by private email.

[johnmorrisoniom]

Just a thought about using "Desktop" as your export folder. If you choose to empty the folder then all of your desktop shortcuts would be deleted, some of which can't, hence why the plugin is freezing

[David Potter]

Hi John. That did cross my mind but I think the Plugin only deletes ged files and media.
Perhaps Mike can clarify

[tatewise]

Yes, the plugin should only delete GEDCOM and Media files that satisfy export filename criteria.
I've run the plugin with my Desktop as the export folder and it uses the folder and empties the folder without a problem.

David, I now have your Project and can recreate the symptoms, so just need to fix the plugin
It is to do with Rich Text format notes that in FH V7 end with an _FMT tag that is sometimes not handled by the plugin.

A temporary workaround is to use Notepad and Replace every _FMT with nothing, leaving blank lines in the GSP GEDCOM file that Gedstar Pro seems to ignore.

[tatewise]

The attached Export Gedcom File plugin Version 5.1.2 Date 10 Dec 2022 should fix the problem, which was caused by Fact Witnesses with Rich Text Notes that were not handled correctly.
It is in compressed ZIP format so it must be extracted before double-clicking the .fh_lua file to install it.

[David Potter]

Thank you Mike. Very much appreciated. Thanks for all your help with this issue.

[tatewise]

Is everything working to your satisfaction?
Let me know so I can delete your Project from my PC.

[David Potter]

Sorry Mike I should have thought to reply with the outcome. Yes all fixed now - Gedstar Pro now handles the exported gedcom file perfectly. And FH when opening the exported gedcom file as a standalone gedcom no longer reports any errors found.

Thank you very much indeed.