* Export GEDCOM plug in problems

[Robert Jacobs]

I'm trying to run Version 4 of the Export GEDCOM plug in FH7. I've set the plug-in for GST & UTF 8.

The plug in locks up at "Analysing input Gedcom SOUR 156"

These errors are reported before the lock-up:

[string "C:\ProgramData\Calico Pie\Family Historian\Pl..."]:6552: attempt to index a nil value (local 'strLine')
stack traceback:
[string "C:\ProgramData\Calico Pie\Family Historian\Pl..."]:6552: in upvalue 'doMediaSeqId'
[string "C:\ProgramData\Calico Pie\Family Historian\Pl..."]:7474: in local 'doFlagObjeUsed'
[string "C:\ProgramData\Calico Pie\Family Historian\Pl..."]:7604: in local 'doAnalyse'
[string "C:\ProgramData\Calico Pie\Family Historian\Pl..."]:9417: in function 'ExportGedcom'
[string "C:\ProgramData\Calico Pie\Family Historian\Pl..."]:9172: in function <[string "C:\ProgramData\Calico Pie\Family Historian\Pl..."]:9162>
(...tail calls...)
[C]: in function 'iuplua.MainLoop'
[string "C:\ProgramData\Calico Pie\Family Historian\Pl..."] in field 'ShowDialogue'
[string "C:\ProgramData\Calico Pie\Family Historian\Pl..."]:9343: in function 'GUI_MainDialogue'
[string "C:\ProgramData\Calico Pie\Family Historian\Pl..."]:9519: in main chunk

[tatewise]

Sorry about that Robert. Can you provide a bit more background please?

Are you a regular user of the Export Gedcom File plugin or is this the first time?

Are you running it in FH v6.2.7 or in the new FH v7.0 ?

If the new FH v7.0 have you just converted the Project from FH v6.2.7 ?

Are you running in a Project or with a standalone GEDCOM file?

In the Export Gedcom File Plugin help page there is a bullet list of checks to perform before using this plugin.
Have you run those checks?

[Robert Jacobs]

Dear Mike,

Mea Culpa. I didn't read the checklist. I am using FH 7.0. I've never before used the Export Gedcom plug-in.

My FH7 file began as an imported GEDCOM from RootsMagic 7. It passes the FH7 validation and media link tests, but there are more than 7500 UDFs. I'm going to see what I can do to repair those. I hope they can be done en masse.

Thanks so much for your help. I'll try to report back when I've figured out how to deal with UDFs.

Robert

[tatewise]

Check out the following FHUG KB advice:
Importing to Family Historian which has a RootsMagic section.
Handling Uncategorised Data Fields i.e. fixing UDF
Compendium of Conversion Plugins

[Robert Jacobs]

All but a dozen of my UDFs are _UID and _AMTID. Is there any reason not to delete them all? What would be the best way to do that?

I'm learning the innards of Family Historian too slowly I fear; although I bought and tried version FH6, I never really used it. I'm preferring FH7 to what I've seen of the interface previews that have been posted for RootsMagic 8.

[tatewise]

Handling Uncategorised Data Fields explains how to do that under The UDF List Plugin.

Getting into importing and exporting is something of a steep learning curve.

Also learning how to use GedSite will be a challenge.
A word of warning, John Cardinal, the GedSite developer, will have only just discovered that FH V7 now uses GEDCOM 5.5.1 instead of GEDCOM 5.5 and that may pose problems with GedSite importing the FH GEDCOM file from the plugin.

[jbtapscott]

For info, when I raised an issue for GedSite last night, John Cardinal responded "......GedSite handles both GEDCOM 5.5.1 and GEDCOM 5.5....."

[Robert Jacobs]

Thank you, and thanks to Mike Tate. I have the plug-in working now and I've turned to fixing the data oddities which resulted from my conversion from RootsMagic.

The issue that I think will be the most difficult is finding a way to output FH7 sentences with the place names pared down to just the first element. I see it can be done in reports with FH7 function calls, but at least according to its manual, GedSite does not recognize the function calls.

I don't plan to address that before I'm satisfied that I've got the written narrative publications set as I want them.

Again, thanks to all.

[tatewise]

I am glad that the plugin now runs OK.
Also, I am in discussion with John Cardinal regarding the GedSite issue which will be fixed in the next plugin release before long.

It may be possible in GedSite to adjust the Place names associated with the {place} code in Sentence Templates.