By Przytula - Thursday, June 10, 2021
|
using latest version genopro on windows created report as always and used gedcom file to upload to openarchives there is a family : cyrille aerts married to louisa gaethofs if looking at louisa : I see a relation to cyrille aerts but not the other way round so in openarchives : I see louisa is married to cyrille but looking at cyrille I do not see louisa this is not the only person having this (FAMS @fam00001@) at Maria-Louisa 0 @ind00001@ INDI 1 NAME Cyrille Leopold /Aerts/ ...
1 FAMC @fam00016@
0 @ind00002@ INDI 1 NAME Maria-Louisa /Gaethofs/ ...
1 FAMS @fam00001@ ...
0 @fam00001@ FAM ...
1 HUSB @ind00001@ 1 WIFE @ind00002@
is this as it should be : generating report on genopro is not a problem ?
best regards, Guy
|
By genome - Saturday, June 12, 2021
|
Please use the Report Generator Skin Template {EN} Export to Gedcom to produce a .ged file compatible with the Gedcom standard.
As I have repeated stated on this forum, the Gedcom Export produced by the built-in version does NOT result in a compatible .ged file but one with some proprietary version dreamt up by the GenoPro author. Hopefully you will also find that much more of your data is transferred when you use the Report Generator veresion.
|
By Przytula - Saturday, June 12, 2021
|
thks for the update I always use : tools - generate report and use the gedfile produced at the end best regards, Guy
|
By genome - Saturday, June 12, 2021
|
Your .ged file is missing a line
1 FAMS @fam00001@
under
0 @ind00001@ INDI1 NAME Cyrille Leopold /Aerts/
This does seem occur when using the built-in Gedcom Export, but not to my knowledge when the Report Generator Export to Gedcom is used. I have tested this on a .gno downloaded from your familytrees site.
|
By Przytula - Monday, June 14, 2021
|
correct I used : tools - generate report - en narrative report and used the ged file produced : not correct now I did the same : tools - generate report - export to gedcom = this is correct many thanks for the update Guy
|