|
By maru-san - Friday, May 30, 2014
|
I used to produce my gedcom file with the Gedcom Export version 2019.12.09 without mayor problems.
Due to some changes recently I wanted to use the latest version 2014.04.05 but it crashed my Genopro Program.
So I wonder what may cause this behavior.
|
|
By appleshaw - Friday, May 30, 2014
|
Using trusty (rusty?) old XP produced a 1700KB report using default profile.
Did you alter any options?
|
|
By maru-san - Friday, May 30, 2014
|
I did not change the options. Creating a gedcom file from one genomap is ok, but creating a gedcom file from all 700 genomaps(app. 78 000 individuals) the program crashes.
Eventually I have to test each genomap, but this is not what I had in mind to do.
|
|
By appleshaw - Saturday, May 31, 2014
|
|
Another file with half that number of individuals is also OK, but only 100 genomaps. If you want to test the genomaps you could try splitting the file into two.
|
|
By genome - Saturday, May 31, 2014
|
700 maps and 78000 individuals is mind-bogglingly huge. I assume some JScript limit has been reached or perhaps there is a loop occurring. I don't have a .gno anywhere near that size to test. I would suggest monitoring GenoPro.exe with Windows Task Manager to check that memory use is not excessive.
What was the feature in the latest version you wanted to use? Is there any error message/number given when the crash occurs?
|
|
By maru-san - Saturday, May 31, 2014
|
The reason for me to use the new version against the old one was the expectation that the new gedom file might be more accurate than the old one.
Attached file shows the result after trying to export a gedcom file after app. 20 minutes. It takes app. this much or longer to created a gedcom file also with the old version.
If you need this file for testing I will send as a PM.
|
|
By genome - Sunday, June 1, 2014
|
|
Yes please send your .gno via PM and I will see if I can reproduce the error and determine where it is going wrong. I will also need details of your Windows version. There are a couple of fixes from Microsoft for similar errors in other packages but I would assume if your are using Windows Update then you should already have these.
|
|
By maru-san - Sunday, June 1, 2014
|
|
Sent by e-mail, since file too big as a PM. Kind of limitation?
|
|
By 602951 - Wednesday, June 18, 2014
|
When I export to gedcom I noticed that any hyperlinks I have from persona in one GenoMap do not automatically link to the corresponding person in another GenoMap.
Is that supposed to be that way? I would have expected that the PersonA in GenoMapA would automatically link to PersonA in GenoMapB.
Is there anyway to make this happen in the gedcom export?
Mike
|
|
By genome - Wednesday, June 18, 2014
|
Hyperlinked individuals are excluded to prevent duplicate entries in the Gedcom output file. Only the 'data source' hyperlinked individual, i.e. the one holding all the data (birth, death, occupations etc.) , is used.
I can see there is a problem when exporting a single GenoMap in that a 'non data source' individual on that GenoMap will be excluded from the output. Is this the scenario you are referring to? I will look for a posible solution to this. e.g. when processing a single GenoMap, also process 'non data source' hyperlinks, retirieving information from the data source, unless the 'data source' is on the same GenoMap i.e. still avoid duplicates.
|
|
By genome - Thursday, June 19, 2014
|
Having done a bit of testing I can see no problem with hyperlinks in the current version. When exporting a single GenoMap with a hyperlinked individual GenoPro appears to collect the data from the data source and add it to the hyperlinked individual. I was therefore mistaken with the comments in my previous post.
So at present I cannot see the problem you are refering to.
|