|
|
|
|
Customers
GenoPro version: 2.0.0.3
Last Login: Wednesday, April 25, 2007
Posts: 4,
Visits: 12
|
Hi
First post, but I have searched for earlier threads regarding my problem.
I am running 2.0.0.4
I am having problems sharing GED's with others as well as uploading to Ancestry. 2 individuals have been unable to open my .ged's. Ancestry shows the following message when I attempt to upload "Error: The file you have specified (xxxx.ged) does not appear to be a valid GEDCOM file, please try again."
I have used both the "Export to Gedcom format" and "Export to Gedcom via Report Generator" options with the same result.
I reduced the names of output and destination files to single words.
I'm at loss on how to proceed. Any suggestions greatly appreciated.
Thanks in advance
Ian G
|
|
|
|
|
Administrators
Moderators
Customers
Gamma
FamilyTrees.GenoPro.com
Translator
GenoPro version: 3.1.0.1
Last Login: Tuesday, February 3, 2026
Posts: 4,886,
Visits: 22,803
|
There may be a tag Ancestry does not like. When you get the error, do you have a line number where the error occurs. A gedcom file may have thousand of lines (entries), and it is very useful to have a mechanism to report which line/tag is not supported.
|
|
|
|
|
Customers
GenoPro version: 2.0.0.3
Last Login: Wednesday, April 25, 2007
Posts: 4,
Visits: 12
|
GenoProSupport (4/22/2007)
There may be a tag Ancestry does not like. When you get the error, do you have a line number where the error occurs. A gedcom file may have thousand of lines (entries), and it is very useful to have a mechanism to report which line/tag is not supported.
The error message didn't give that much detail - I pasted the entire message in my original post. Also, I have 2 friends who have been unable to open .ged's I've created. One uses Legacy and she told me that trying to open my GED caused another GED to open. I don't know which software the other friend is using, but she reported not being able to open.
I'm prepared to accept that it's user error, but I just don't know where I'm making my mistake. It might be something daft like improper filename syntax. I'll attach it here, but I ask anyone who opens it not to use it or distribute it - it's really half-baked at this point. Anyone interested in the families involved can PM me here and I'll be happy to share all I have.
Thanks
Ian G
Gillis.ged
(89 views,
58.02 KB)
|
|
|
|
|
Administrators
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1
Last Login: 50 minutes ago
Posts: 3,487,
Visits: 27,240
|
The Gedcom file you have posted is generated using the built-in Export to Gedcom. You should have better luck with the 'Export to Gedcom' using the Report Generator. Be sure to select the 'Export to Gedcom {EN}' skin.
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
|
|
|
|
|
Customers
GenoPro version: 2.0.0.3
Last Login: Wednesday, April 25, 2007
Posts: 4,
Visits: 12
|
Ron (4/22/2007)
The Gedcom file you have posted is generated using the built-in Export to Gedcom. You should have better luck with the 'Export to Gedcom' using the Report Generator. Be sure to select the 'Export to Gedcom {EN}' skin.
Hi Ron
I've tried both methods and Ancestry didn't like either version of the file. And, yes, I did select the skin you mention above.
Does it make a difference that I'm converting only one genomap from my tree? I previously cut and pasted part of one .gno file into a new file and successfully converted that using the reports generator. I could try that again, but I'd be happier if I could avoid extra steps.
Thanks
Ian G
|
|
|
|
|
Administrators
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.1.0.1
Last Login: 50 minutes ago
Posts: 3,487,
Visits: 27,240
|
May be Ancestry.com is just a little flakey at times. I converted your .ged file to a 'Report Generator' gedcom by importing it into GenoPro (this should result in an identical .gno to yours) and re-exporting using the Report Generator. I was then able to import this tree into a non-public Ancestry.com tree using IE6 without any problem. I have now deleted this tree. Ancestry seems to abort transactions at busy times - it took several attempts before the tree was deleted.
'lego audio video erro ergo disco' or "I read, I listen, I watch, I make mistakes, therefore I learn"
|
|
|
|
|
Customers
Important Contributors
FamilyTrees.GenoPro.com
GenoPro version: 3.0.1.5
Last Login: Saturday, March 14, 2020
Posts: 365,
Visits: 3,680
|
I used an earlier version of GenoPro to generate a Ged file for Ancestry and had no problem uploading it.I had had problems with GenesReunited earlier but had removed the custom tags and it then worked. I can't remember which version I used but it was last Christmas. I intend to update these sites again at the beginning of summer so am curious to know if there is a bug.
Edited: Sunday, April 22, 2007 by
IainTait
|
|
|
|
|
Customers
GenoPro version: 2.5.4.0
Last Login: Sunday, September 20, 2015
Posts: 64,
Visits: 1,814
|
I had a similar problem importing a GED from Genopro in either Legacy or PAF (I forget which).
The problem seemed to be with the DEAT (death tag).
Genopro exports DEAT Y.
Using a text editor I changed all occurrences to DEAT and the file was accepted.
I avoid all Genopro custom tags in my tree for this reason.
Genopro is wonderful for the display of a graphic tree particularly the ability to extract a portion of my tree, create an EMF and paste onto a page in a Word document or create a PDF of the diagram to pass onto others.
But unfortunatley the program lacks the tools to produce text files in report format for Descendant, Ahnentafel and Descendant Narrative reports.
I find these essential when passing data on to non-Genopro users.
So I'm stuck with exporting GEDCOM files to third party software for this convenience.
|
|
|
|
|
Customers
GenoPro version: 2.0.0.3
Last Login: Wednesday, April 25, 2007
Posts: 4,
Visits: 12
|
Barry Graham (4/22/2007)
I had a similar problem importing a GED from Genopro in either Legacy or PAF (I forget which).
The problem seemed to be with the DEAT (death tag).
Genopro exports DEAT Y.
Using a text editor I changed all occurrences to DEAT and the file was accepted.
I avoid all Genopro custom tags in my tree for this reason.
Genopro is wonderful for the display of a graphic tree particularly the ability to extract a portion of my tree, create an EMF and paste onto a page in a Word document or create a PDF of the diagram to pass onto others.
But unfortunatley the program lacks the tools to produce text files in report format for Descendant, Ahnentafel and Descendant Narrative reports.
I find these essential when passing data on to non-Genopro users.
So I'm stuck with exporting GEDCOM files to third party software for this convenience.
Hi
You're right on the money about why I chose GenoPro - the ability to share with folks who don't have GEDCOM viewers, or even computers. The PDF output appeals to me, though I haven't played with that yet. After reading the first few responses I was already thinking that one software package might not be enough, so I may pick up Legacy to complement GenoPro. Since I decided to drop $300 on Ancestry, software seems pretty cheap.
I'll check out the DEAT tag issue too.
Thanks to all who responded !
Ian G
|