|
|
Post by tirerim on Jan 25, 2011 3:01:57 GMT -5
In certain circumstances, it is possible to get into an infinite loop with the error
"System Error 03
Can't find current family in this person's families".
Clicking the Quit button just brings up the same error again, and the only way to get out is with Force Quit.
The problem seems to occur in the following circumstance: suppose INDI1 and INDI2 are the husband and wife of FAM1, and while INDI1 correctly lists FAM1, INDI2 doesn't (probably because the original GEDCOM file was malformed and just didn't have the family line for INDI2). If you are viewing INDI1, and click on INDI2, you get stuck in the error loop.
It's possible to select the person by using "Find Person", but then their spouse and children don't show up, and there doesn't seem to be an obvious way to add them (though I might just be missing that). (I suspect that exporting the entire tree back to GEDCOM, manually fixing the missing lines, and re-importing it will work, but that's kind of a pain.) Ideally, instead of the error the program should offer to add the missing family to the individual.
|
|
|
|
Post by Howard Metcalfe on Jan 25, 2011 12:51:09 GMT -5
In certain circumstances, it is possible to get into an infinite loop with the error "System Error 03 Can't find current family in this person's families". Clicking the Quit button just brings up the same error again, and the only way to get out is with Force Quit. The problem seems to occur in the following circumstance: suppose INDI1 and INDI2 are the husband and wife of FAM1, and while INDI1 correctly lists FAM1, INDI2 doesn't (probably because the original GEDCOM file was malformed and just didn't have the family line for INDI2). If you are viewing INDI1, and click on INDI2, you get stuck in the error loop. It's possible to select the person by using "Find Person", but then their spouse and children don't show up, and there doesn't seem to be an obvious way to add them (though I might just be missing that). (I suspect that exporting the entire tree back to GEDCOM, manually fixing the missing lines, and re-importing it will work, but that's kind of a pain.) Ideally, instead of the error the program should offer to add the missing family to the individual. You're correct that the original GEDCOM is malformed. One of the things you should do after importing a GEDCOM is to immediately check linkages using File menu > Analyze > Linkage (or command-K). That would have done what you wanted: offer to add the missing family to the individual.You can probably do that now and it probably will fix the malformation. I always do a command-K before doing File menu > Write Text > List of Possible Problems (command-L). In fact, I do the command-K command-L sequence frequently just to clean up any possible problems, as well as after importing a GEDCOM. Note that PAWriter (as with other programs) may be unable to fix severely malformed GEDCOMs. That's just life -- a program cannot be a mind reader. In those cases, you will have to endure the pain and fix the GEDCOM in a text editor, or just forget it. Also, make sure you read the topic "Importing a GEDCOM into an existing file" under FAQs in this forum. Best, Howard |
|
|
|
Post by tirerim on Jan 27, 2011 0:49:39 GMT -5
You're correct that the original GEDCOM is malformed. One of the things you should do after importing a GEDCOM is to immediately check linkages using File menu > Analyze > Linkage (or command-K). That would have done what you wanted: offer to add the missing family to the individual.You can probably do that now and it probably will fix the malformation. I always do a command-K before doing File menu > Write Text > List of Possible Problems (command-L). In fact, I do the command-K command-L sequence frequently just to clean up any possible problems, as well as after importing a GEDCOM. Note that PAWriter (as with other programs) may be unable to fix severely malformed GEDCOMs. That's just life -- a program cannot be a mind reader. In those cases, you will have to endure the pain and fix the GEDCOM in a text editor, or just forget it. Also, make sure you read the topic "Importing a GEDCOM into an existing file" under FAQs in this forum. Ah, thanks, that's very useful to know about. As it turns out, before I got your reply I was able to write a script to fix the original file (there were about a hundred entries like that, probably owing to my previous program being a piece of junk), but I expect that I will be using command-K in the future. And the command-L report should be a very useful start on a long-planned cleanup. Though I still maintain that no program should return the kind of error that requires a force quit -- perhaps it could simply go back to the previously selected person after displaying the error message? :-) |
|
|
|
Post by Howard Metcalfe on Jan 27, 2011 12:18:52 GMT -5
You're correct that the original GEDCOM is malformed. One of the things you should do after importing a GEDCOM is to immediately check linkages using File menu > Analyze > Linkage (or command-K). That would have done what you wanted: offer to add the missing family to the individual.You can probably do that now and it probably will fix the malformation. I always do a command-K before doing File menu > Write Text > List of Possible Problems (command-L). In fact, I do the command-K command-L sequence frequently just to clean up any possible problems, as well as after importing a GEDCOM. Note that PAWriter (as with other programs) may be unable to fix severely malformed GEDCOMs. That's just life -- a program cannot be a mind reader. In those cases, you will have to endure the pain and fix the GEDCOM in a text editor, or just forget it. Also, make sure you read the topic "Importing a GEDCOM into an existing file" under FAQs in this forum. Ah, thanks, that's very useful to know about. As it turns out, before I got your reply I was able to write a script to fix the original file (there were about a hundred entries like that, probably owing to my previous program being a piece of junk), but I expect that I will be using command-K in the future. And the command-L report should be a very useful start on a long-planned cleanup. Though I still maintain that no program should return the kind of error that requires a force quit -- perhaps it could simply go back to the previously selected person after displaying the error message? :-) You'd be surprised how many commercial programs (programs that you pay for) I've used that have once in a awhile required a force quit! In any case, doing the command-K should avoid the force quit if done immediately after import. There are a jillion possible malformations in GEDCOMs and some times I think I've run into them all; most end up undetectable on import but will be caught with command-K before you need to force quit. Many are unrecoverable. But maybe I should think about doing the linkage check on every import, although I would rather the user ask for it. Trying to continue processing when a malformation is detected could be disastrous; the problem won't go away and may just ripple through other entries and/or crash again. So that's not a solution. Best, Howard |
|
