|
|
|
Junior Member
 
Group: Customers
Last Login: 2 days ago @ 8:28:23 AM
GenoPro Version: 2.0.1.5
Posts: 15,
Visits: 90
|
|
I have read the various threads regarding the problems involved in exporting gedcoms to other packages and the skins that have been prepared in the past to remedy this, but, with the release of genopro 2007 the situation doesnt seem to have been resolved as I hoped it would.
Over the past few years I have been using Genopro in its beta forms to create a tree that I then regularly export into both ancestry.com and genesreunited. Until November all was fine. But now both websites complain that the gedcom from Genopro is not a valid gedcom and will no longer upload it. Very frustrating...
I am presuming that the trouble is with the Genopro gedcom, and not with my tree having become corrupted in some way. And that size (3700 people) isnt a factor...
Any suggestions?
|
|
|
|
|
Forum Member
Group: Customers
Last Login: 1/1/2008 5:04:58 PM
GenoPro Version: 2.0.1.4
Posts: 36,
Visits: 93
|
|
| Hi, I use the 2007 export to Ancestry.com and have no problems...
|
|
|
|
|
Grand Master
Group: Customers
Last Login: Today @ 10:20:31 AM
GenoPro Version: 2.0.1.6
Posts: 1,145,
Visits: 5,355
|
|
GenoPro has two types of Gedcom export. 'Export to Gedcom' via the Report Generator should produce a Gedcom 5.5 compatible file. If it does not then I would like to fix the problem. Please give an example of the error you are getting when importing in to other packages, together with an extract containing the erroneous data in your .ged file. Change the details to protect the innocent if required.
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
|
|
|
|
|
Famous Writer
Group: Customers
Last Login: 11/13/2008 6:10:56 AM
GenoPro Version: 2.0.1.4
Posts: 438,
Visits: 3,412
|
|
| Hi Ron, I made a Ged file with your report generator and it uploaded to GenesReunited perfectly at the first try whereas before I had had lots of problems. I also uploaded it to Ancestry with the same ease. I noticed however that when I opened the one made with your generator and that made when an html report is generated, they were different.
|
|
|
|
|
Junior Member
Group: Customers
Last Login: 2 days ago @ 8:28:23 AM
GenoPro Version: 2.0.1.5
Posts: 15,
Visits: 90
|
|
I am still having the problem of uploading a gedcom onto ancestry.com.
This is what ancestry says:
Error: The file you have specified (BigOne 010107.ged) does not appear to be a valid GEDCOM file, please try again.
I have tried using Legacy to produce a 5.5 format gedcom using their export facility but no change. Though it re-imports into genopro OK.
Following your suggestion of using Export via report generator, I got this:
[0.00] Processing template 'Gedcom.js'...
Some OCCU data missing due to unprocessed Custom Tag (Gedcom) in GenoPro file for ind06602
[15.14]
Some OCCUpation data fields maybe missing from the output Gedcom file as indicated above due to unprocessed Custom Tags holding original Gedcom import OCCU tag data.
To correct this, examine the Custom Tags of the individuals flagged above and move the data from any Custom Tags with a "occupation." prefix to the correct occupation record for this individual and then delete these Custom Tags. You can use the "View/Table Layout - Individuals" and right click each such Custom Tag column and choose "Delete Custom Tag x...x" from the context menu. You can then run this report again
Gedcom output has been written to file C:\Documents and Settings\Rob Tylor\My Documents\family trees\genopro report\BigOne 301206.ged
Generated and written 1 page in 15.360 seconds
1 errors encountered while generating report!
[15.45] Writing files from skin...
[15.45] Writing pictures to report (1)...
[15.45] Report Ready! Click on the "Close" button to continue.
And have now deleted the custom tags and tried everything again - but no change, using the gedcom generated after the deletion....
And now I have produced a very small test tree (just 3 people) and still no joy... same 'not a valid gedcom' from ancestry.com
How frustrating...
What would you need in order to help with this problem?
But, it isnt genopro. I just tried creating a small tree using Legacy, exporting as a 5.5 gedcom and still get a 'not a vaild gedcom' from ancestry.com. I have now written to their help line....
Thanks
Rob
|
|
|
|
|
Forum Guru
Group: Customers
Last Login: Yesterday @ 10:48:09 AM
GenoPro Version: 2.0.1.6
Posts: 191,
Visits: 2,741
|
|
Could you please attach this newly generated .ged (and the affected .gno)?
Feri
|
|
|
|
|
Famous Writer
Group: Customers
Last Login: 11/13/2008 6:10:56 AM
GenoPro Version: 2.0.1.4
Posts: 438,
Visits: 3,412
|
|
| I did not use the "File" dropdown menu "Export to Gedcom format". I used the Report Generator, choose the "destination folder", choose "data source" (your tree), choose the skin "Export to Gedcom" and then Generate. This produces a Ged file 5.5 which I uploaded to Ancestry with no problem. 
|
|
|
|
|
Forum Writer
Group: Customers
Last Login: 2 days ago @ 7:32:17 PM
GenoPro Version: 2.0.1.1
Posts: 66,
Visits: 660
|
|
I have used the GEDCOM produced by the report generator to upload to Rootsweb.
It was accepted OK but there was one problem.
The GEDCOM death field from Genopro was DEAT Y.
When uploaded this caused the Rootsweb display to ignore the date of death.
Using a search and replace on the text of the GEDCOM to change DEAT Y to DEAT solved the problem.
|
|
|
|
|
Forum Guru
Group: Customers
Last Login: Yesterday @ 10:48:09 AM
GenoPro Version: 2.0.1.6
Posts: 191,
Visits: 2,741
|
|
Unfortunately, the gedcom spec is not a 100% clear one (and does not contain extension specs as well :(). Ron wrote in a topic, that he would like to make an export report to be compliant with the ged 5.5 version (as v6 specs seems to be dead).
The help him you really must attach the .gno and the .ged as the report result  . Ron will definitely have a look on that - but if no details, no valuable answer so far...
Feri
|
|
|
| | |