On 5/16/2016 3:48 PM, Charlie Hoffpauir wrote: > On 5/16/2016 3:08 PM, Jesse Davis wrote: >> I just created a NEHGS descendant list with no problems. >> It had 2500 pages, 4062 sources and about 31750 names. >> I am using version 7.2.0.0 on WIN7. >> J Davis > Jesse, > > Thanks for that feedback. I just tried again, and it seems that the > problem I'm getting is when RM attempts to save the list as a PDF. > This time I first saved it as an RTF file, which opened fine in Word. > But I then tried to save it as a PDF and it once again locked up. so > now I at least have the problem narrowed down. I closed the program > (again using Task manager) and re-opened and this time choose only 4 > generations, and this time the program generated the PDF just fine. > I'll keep testing and post again when I determine at just how many > generations the lockup occurs.... although based on your data, it > seems to handle much larger data sets than mine. (My RTF file resulted > in a Word doc file of 973 pages, I don't know how many names that is, > but it's got to be much less than my entire database of 33783 people) > > I just noticed that you mentioned that you created a NEHGS descendant > list. I was NOT generating that kind of narrative report.... just a > simple Descendant list showing names of descendants, their spouse, and > birth and death date. <snip> This is not working out as expected. This time I got a Range Error message from RM instead of completing the generation of the list, when I had worked up to 7 generations of descendants. This makes me wonder if the earlier list I'd generated is complete, or if it's missing many names, since it was set for 10 generations, and the program "completed" the report. All in all I have to say that this is very disturbing. I did check the box showing the Range Error to send information to RM about the problem. -- Charlie Hoffpauir http://my.rootsmagic.com/CRHoffpauir/ http://sites.rootsmagic.com/CharlieHoffpauir/ http://freepages.genealogy.rootsweb.com/~charlieh/ http://www.familytreedna.com/group-join.aspx?Group=Hoffpauir

I know you have used RM a long time, but -- Just in case -- Did you run the database tools? Joy On 5/16/2016 2:05 PM, Charlie Hoffpauir via wrote: > On 5/16/2016 3:48 PM, Charlie Hoffpauir wrote: >> On 5/16/2016 3:08 PM, Jesse Davis wrote: >>> I just created a NEHGS descendant list with no problems. >>> It had 2500 pages, 4062 sources and about 31750 names. >>> I am using version 7.2.0.0 on WIN7. >>> J Davis >> Jesse, >> >> Thanks for that feedback. I just tried again, and it seems that the >> problem I'm getting is when RM attempts to save the list as a PDF. >> This time I first saved it as an RTF file, which opened fine in Word. >> But I then tried to save it as a PDF and it once again locked up. so >> now I at least have the problem narrowed down. I closed the program >> (again using Task manager) and re-opened and this time choose only 4 >> generations, and this time the program generated the PDF just fine. >> I'll keep testing and post again when I determine at just how many >> generations the lockup occurs.... although based on your data, it >> seems to handle much larger data sets than mine. (My RTF file resulted >> in a Word doc file of 973 pages, I don't know how many names that is, >> but it's got to be much less than my entire database of 33783 people) >> >> I just noticed that you mentioned that you created a NEHGS descendant >> list. I was NOT generating that kind of narrative report.... just a >> simple Descendant list showing names of descendants, their spouse, and >> birth and death date. > <snip> > This is not working out as expected. This time I got a Range Error > message from RM instead of completing the generation of the list, when I > had worked up to 7 generations of descendants. This makes me wonder if > the earlier list I'd generated is complete, or if it's missing many > names, since it was set for 10 generations, and the program "completed" > the report. All in all I have to say that this is very disturbing. I did > check the box showing the Range Error to send information to RM about > the problem. > --- This email has been checked for viruses by Avast antivirus software. https://www.avast.com/antivirus

I needed a break. So I started to play. I tried generating a 300 generation list. After 30 minutes, I cancelled it. Then I tried 100 generations; that generated an error. Then I tried 50, then 25, then 15; all of them generated an error. So I went back to the default 10 generations and no problem. It was very fast. Then I started to increase the number of generations: 11, 12, and 13. Each list got progressively slower. It generated an error again at 14. Saving to a pdf was no problem at 13 generations. I am glad I don't use descendants lists very often. Ken Sent from my iPhone > On May 16, 2016, at 2:05 PM, Charlie Hoffpauir via <rootsmagic-users@rootsweb.com> wrote: > >> On 5/16/2016 3:48 PM, Charlie Hoffpauir wrote: >>> On 5/16/2016 3:08 PM, Jesse Davis wrote: >>> I just created a NEHGS descendant list with no problems. >>> It had 2500 pages, 4062 sources and about 31750 names. >>> I am using version 7.2.0.0 on WIN7. >>> J Davis >> Jesse, >> >> Thanks for that feedback. I just tried again, and it seems that the >> problem I'm getting is when RM attempts to save the list as a PDF. >> This time I first saved it as an RTF file, which opened fine in Word. >> But I then tried to save it as a PDF and it once again locked up. so >> now I at least have the problem narrowed down. I closed the program >> (again using Task manager) and re-opened and this time choose only 4 >> generations, and this time the program generated the PDF just fine. >> I'll keep testing and post again when I determine at just how many >> generations the lockup occurs.... although based on your data, it >> seems to handle much larger data sets than mine. (My RTF file resulted >> in a Word doc file of 973 pages, I don't know how many names that is, >> but it's got to be much less than my entire database of 33783 people) >> >> I just noticed that you mentioned that you created a NEHGS descendant >> list. I was NOT generating that kind of narrative report.... just a >> simple Descendant list showing names of descendants, their spouse, and >> birth and death date. > <snip> > This is not working out as expected. This time I got a Range Error > message from RM instead of completing the generation of the list, when I > had worked up to 7 generations of descendants. This makes me wonder if > the earlier list I'd generated is complete, or if it's missing many > names, since it was set for 10 generations, and the program "completed" > the report. All in all I have to say that this is very disturbing. I did > check the box showing the Range Error to send information to RM about > the problem. > > -- > Charlie Hoffpauir > > http://my.rootsmagic.com/CRHoffpauir/ > http://sites.rootsmagic.com/CharlieHoffpauir/ > http://freepages.genealogy.rootsweb.com/~charlieh/ > http://www.familytreedna.com/group-join.aspx?Group=Hoffpauir > > > > > =================================== > RM list Archives: http://archiver.rootsweb.com/th/index/ROOTSMAGIC-USERS/ > http://archiver.rootsweb.com/cgi-bin/search?path=ROOTSMAGIC-USERS > WISH LIST: http://www.rootsmagic.com/forums/ BLOG: http://blog.rootsmagic.com/ > > > ------------------------------- > To unsubscribe from the list, please send an email to ROOTSMAGIC-USERS-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message

On 5/16/2016 5:23 PM, Harringkbat wrote: > I needed a break. So I started to play. I tried generating a 300 generation list. After 30 minutes, I cancelled it. Then I tried 100 generations; that generated an error. Then I tried 50, then 25, then 15; all of them generated an error. > > So I went back to the default 10 generations and no problem. It was very fast. Then I started to increase the number of generations: 11, 12, and 13. Each list got progressively slower. It generated an error again at 14. > > Saving to a pdf was no problem at 13 generations. > > I am glad I don't use descendants lists very often. > > Ken > > Sent from my iPhone Ken, Thanks for the feedback. It must be something "other" than the pure "number" of generations before the error occurs, because now I'm getting the error at 8 generations versus your seeing it at 14 with your database. My error is: "RootsMagic has encountered ad unexpected error: Range check error" "Please tell RootsMagic about this problem" I know I had this problem several versions ago, and I'm pretty sure that it was "fixed", but like you, I don't often generate such a list.... I only tried it today thinking it might be appropriate for the upcoming family reunion. I really believe that this worked fine in version 6..... when I have time I'm going to try to go back to version 6 and check it out. With that in mind, does anyone know if it's possible to download a previous version? >> On May 16, 2016, at 2:05 PM, Charlie Hoffpauir via <rootsmagic-users@rootsweb.com> wrote: >> >>> On 5/16/2016 3:48 PM, Charlie Hoffpauir wrote: >>>> On 5/16/2016 3:08 PM, Jesse Davis wrote: >>>> I just created a NEHGS descendant list with no problems. >>>> It had 2500 pages, 4062 sources and about 31750 names. >>>> I am using version 7.2.0.0 on WIN7. >>>> J Davis >>> Jesse, >>> >>> Thanks for that feedback. I just tried again, and it seems that the >>> problem I'm getting is when RM attempts to save the list as a PDF. >>> This time I first saved it as an RTF file, which opened fine in Word. >>> But I then tried to save it as a PDF and it once again locked up. so >>> now I at least have the problem narrowed down. I closed the program >>> (again using Task manager) and re-opened and this time choose only 4 >>> generations, and this time the program generated the PDF just fine. >>> I'll keep testing and post again when I determine at just how many >>> generations the lockup occurs.... although based on your data, it >>> seems to handle much larger data sets than mine. (My RTF file resulted >>> in a Word doc file of 973 pages, I don't know how many names that is, >>> but it's got to be much less than my entire database of 33783 people) >>> >>> I just noticed that you mentioned that you created a NEHGS descendant >>> list. I was NOT generating that kind of narrative report.... just a >>> simple Descendant list showing names of descendants, their spouse, and >>> birth and death date. >> <snip> >> This is not working out as expected. This time I got a Range Error >> message from RM instead of completing the generation of the list, when I >> had worked up to 7 generations of descendants. This makes me wonder if >> the earlier list I'd generated is complete, or if it's missing many >> names, since it was set for 10 generations, and the program "completed" >> the report. All in all I have to say that this is very disturbing. I did >> check the box showing the Range Error to send information to RM about >> the problem. >> >> -- >> Charlie Hoffpauir >> >> -- Charlie Hoffpauir http://my.rootsmagic.com/CRHoffpauir/ http://sites.rootsmagic.com/CharlieHoffpauir/ http://freepages.genealogy.rootsweb.com/~charlieh/ http://www.familytreedna.com/group-join.aspx?Group=Hoffpauir

HOW did you manage to create a database back 300 generations???? I am jealous!!!!! Pat Mc -----Original Message----- From: rootsmagic-users-bounces@rootsweb.com [mailto:rootsmagic-users-bounces@rootsweb.com] On Behalf Of Harringkbat via Sent: Monday, May 16, 2016 6:24 PM To: Charlie Hoffpauir; rootsmagic-users@rootsweb.com Subject: Re: [RMagic] RM crashing in creating a large descendants list. I needed a break. So I started to play. I tried generating a 300 generation list. After 30 minutes, I cancelled it. Then I tried 100 generations; that generated an error. Then I tried 50, then 25, then 15; all of them generated an error. So I went back to the default 10 generations and no problem. It was very fast. Then I started to increase the number of generations: 11, 12, and 13. Each list got progressively slower. It generated an error again at 14. Saving to a pdf was no problem at 13 generations. I am glad I don't use descendants lists very often. Ken Sent from my iPhone > On May 16, 2016, at 2:05 PM, Charlie Hoffpauir via <rootsmagic-users@rootsweb.com> wrote: > >> On 5/16/2016 3:48 PM, Charlie Hoffpauir wrote: >>> On 5/16/2016 3:08 PM, Jesse Davis wrote: >>> I just created a NEHGS descendant list with no problems. >>> It had 2500 pages, 4062 sources and about 31750 names. >>> I am using version 7.2.0.0 on WIN7. >>> J Davis >> Jesse, >> >> Thanks for that feedback. I just tried again, and it seems that the >> problem I'm getting is when RM attempts to save the list as a PDF. >> This time I first saved it as an RTF file, which opened fine in Word. >> But I then tried to save it as a PDF and it once again locked up. so >> now I at least have the problem narrowed down. I closed the program >> (again using Task manager) and re-opened and this time choose only 4 >> generations, and this time the program generated the PDF just fine. >> I'll keep testing and post again when I determine at just how many >> generations the lockup occurs.... although based on your data, it >> seems to handle much larger data sets than mine. (My RTF file >> resulted in a Word doc file of 973 pages, I don't know how many names >> that is, but it's got to be much less than my entire database of >> 33783 people) >> >> I just noticed that you mentioned that you created a NEHGS descendant >> list. I was NOT generating that kind of narrative report.... just a >> simple Descendant list showing names of descendants, their spouse, >> and birth and death date. > <snip> > This is not working out as expected. This time I got a Range Error > message from RM instead of completing the generation of the list, when > I had worked up to 7 generations of descendants. This makes me wonder > if the earlier list I'd generated is complete, or if it's missing many > names, since it was set for 10 generations, and the program "completed" > the report. All in all I have to say that this is very disturbing. I > did check the box showing the Range Error to send information to RM > about the problem. > > -- > Charlie Hoffpauir > > http://my.rootsmagic.com/CRHoffpauir/ > http://sites.rootsmagic.com/CharlieHoffpauir/ > http://freepages.genealogy.rootsweb.com/~charlieh/ > http://www.familytreedna.com/group-join.aspx?Group=Hoffpauir > > > > > =================================== > RM list Archives: > http://archiver.rootsweb.com/th/index/ROOTSMAGIC-USERS/ > http://archiver.rootsweb.com/cgi-bin/search?path=ROOTSMAGIC-USERS > WISH LIST: http://www.rootsmagic.com/forums/ BLOG: > http://blog.rootsmagic.com/ > > > ------------------------------- > To unsubscribe from the list, please send an email to > ROOTSMAGIC-USERS-request@rootsweb.com with the word 'unsubscribe' > without the quotes in the subject and the body of the message =================================== RM list Archives: http://archiver.rootsweb.com/th/index/ROOTSMAGIC-USERS/ http://archiver.rootsweb.com/cgi-bin/search?path=ROOTSMAGIC-USERS WISH LIST: http://www.rootsmagic.com/forums/ BLOG: http://blog.rootsmagic.com/ ------------------------------- To unsubscribe from the list, please send an email to ROOTSMAGIC-USERS-request@rootsweb.com with the word 'unsubscribe' without the quotes in the subject and the body of the message

Ken, regardless of the number of generations in your database, it should not matter how many you specify for the report, within reason. There is a limit of 32 for reports that use Ahnentafel numbering. The testing you have done is perfectly valid in trying to ascertain a breaking point. I daresay that there is a generational loop in both yours and Charlie's databases that comes into play at fewer than the number of generations at which you detect a slowdown. By that I mean you have an ancestor linked to himself also as a descendant. In RM, there is no tool to find such loops. There is in some other software. You might detect it by visual inspection of the report you succeeded in getting - there should be much repetition. Tom On Mon, May 16, 2016 at 6:23 PM, Harringkbat via < rootsmagic-users@rootsweb.com> wrote: > I needed a break. So I started to play. I tried generating a 300 > generation list. After 30 minutes, I cancelled it. Then I tried 100 > generations; that generated an error. Then I tried 50, then 25, then 15; > all of them generated an error. > > So I went back to the default 10 generations and no problem. It was very > fast. Then I started to increase the number of generations: 11, 12, and 13. > Each list got progressively slower. It generated an error again at 14. > > Saving to a pdf was no problem at 13 generations. > > I am glad I don't use descendants lists very often. > > Ken > > > >