Login to participate
  
       
Register   Lost ID/password?
The Behold User Forum » Topic           prev Prev   Next next

Lockups upon importng gedcoms with notes - Categorized in: Report a ProblemReport a Problem

8 posts. Started 18 Jun 2006 by MaxHaiflichJr. Latest reply 17 Mar 2007 by lkessler. RSS 2.0 feed for this topic RSS
1. Max Haiflich (MaxHaiflichJr)
United States flag
Joined: Sun, 7 May 2006
0 blog comments, 13 forum posts
Posted: Sun, 18 Jun 2006 Permalink
I've run into a minor problem with loading gedcoms that include certain gedcom key symbols in a note field. If things like @ or / are included in a NOTE, Behold locks up. Eliminating those symbols from the NOTE in the gedcom solves the problem for me, but others may not know how.

I've also run into another lockup problem that I haven't pinpointed yet. It only happens while importing multiple gedcoms together. Loading any one of the same gedcoms individually works fine.

I'm using Behold version 0.98.5 Alpha.

Max haiflich, Jr.
2. Louis Kessler (lkessler)
Canada flag
Joined: Sun, 9 Mar 2003
137 blog comments, 200 forum posts
Posted: Sun, 18 Jun 2006 Permalink
Max: I've tried, but I cannot create the problem.

Could you give me an example of what one of the NOTE lines looks like that causes the problem?

Louis
3. Max Haiflich (MaxHaiflichJr)
United States flag
Joined: Sun, 7 May 2006
0 blog comments, 13 forum posts
Posted: Mon, 19 Jun 2006 Permalink
Louis,

Not a problem. Here it is:

1 SOUR @S01@
2 PAGE Alan Senescal Of Dol 1020 AF Walter Stewart abt 1180.ged
2 DATA
3 TEXT Alan, Senescal Of Dol SEX M
4 CONT TITL Senescal Of Dol
4 CONT AFN HPFN-02
4 CONT BIRT 1020? Of, Dol-De-Bretagne, Ille-Et-Vilaine, France
4 CONT FAMS @F4708041@
3 DATE 5 Jan 1998

On the next to last line, I forgot to exclude the @ symbols in the FAMS IDN. When I loaded a gedcom similar to this (it also had the @ symbols around the AFN # in it), Behold locked up.

When I eliminated the @ symbols Behold loaded it just fine.

However, now that I think about it, that may have been before I updated to the newest version. It was a minor glitch that I worked around and then put off reporting for a while.

The other problem, i haven't fully figured out yet and haven't had much time to study it.

Max
4. Louis Kessler (lkessler)
Canada flag
Joined: Sun, 9 Mar 2003
137 blog comments, 200 forum posts
Posted: Mon, 19 Jun 2006 Permalink
Max:

It should not matter whether that particular line has the @ symbols or not. That line is a continuation of a text comment and Behold should handle it.

I put that exact code with the @ symbols into a simple test program and I couldn't get Behold to fail. I tried several earlier versions of Behold as well but they handled it.

Behold should NEVER lock up. That is something I would very much like to fix. Would you be able to e-mail me the complete GEDCOM of the file that fails?

Thanks.

Louis
5. Max Haiflich (MaxHaiflichJr)
United States flag
Joined: Sun, 7 May 2006
0 blog comments, 13 forum posts
Posted: Mon, 19 Jun 2006 Permalink
Louis,

Sorry, the original files that I had the problem with have already been changed and I can't recreate the lockup as Behold handles the other files with the @ symbols with no problem. Maybe, it was a glitch in my computer at the time and it corrected itself on the next restart.

I can recreate the other problem and will send you files that do it and explain what's happening. But, it has nothing to do with symbols or notes, as far as I can determine.

Max
6. Margaret Chaney (Mala)
United States flag
Joined: Sun, 16 Jul 2006
0 blog comments, 1 forum post
Posted: Mon, 17 Jul 2006 Permalink
I just today downloaded Behold Version 98.5 and after looking over the Quick Start and playing around with the Clinton.GED, I downloaded one of my GED files. While browsing through the various features, the file stopped responding. I have no idea why this happened, however, the Microsoft troubleshooting service (the little box that pops up, notifying you that an error has occurred and a report is being prepared to be sent to Microsoft) provided several bits of information which I PrintScreened and pasted into Word. I have tried unsuccessfully to track this error report through Microsoft, but apparently lack the expertise to know how to do this. Their site states that if the error involved third party vendors the report would be sent to them. Since you indicated you were especially interested in resolving lockup problems with Behold, and since there is a report reflecting exactly what happened, I thought you might want to check it out.
7. Louis Kessler (lkessler)
Canada flag
Joined: Sun, 9 Mar 2003
137 blog comments, 200 forum posts
Posted: Tue, 18 Jul 2006 Permalink
Thanks, Mala, for reporting this. Yes, I do want to fix it.

I usually have to be able to reproduce the error myself so that I can trace where it is happening and fix it. The easiest way for me to do this is if I had a copy of the GEDCOM you used that produced the error. If you wouldn't mind sending it to me, my e-mail address is at the bottom of all my web pages.

Sorry about the Microsoft error. I'll also see if I can find a way to trap the error before that silly Microsoft box comes up.

Louis
8. Louis Kessler (lkessler)
Canada flag
Joined: Sun, 9 Mar 2003
137 blog comments, 200 forum posts
Posted: Tue, 25 Jul 2006 Permalink

I've done some work to prevent certain types of lockups in Behold, and this will be in the next version. It will prevent you from interrupting a processing task with another processing task. See the July 25, 2006 entry in my Behold Blog for more details.

Leave your Reply

You must login to post your reply.

Login to participate
  
       
Register   Lost ID/password?