Pat, there is no way that would be possible!!!!! 300 generations, at about 25 years per generation, would be about 7,500 years ago. Ken, have you discovered some kind of crystal ball that lets you look back that far? Why would anyone even try to do a 300, 100, 50, or 25 generation list? Utter nonsense! Yeah, I know, some "researchers" have traced their ancestors back to Adam and Eve. Don't know how many generations that would be. George At 16-05-2016 07:35 PM Monday, you wrote: *********START OF ORIGINAL MESSAGE TEXT********* >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 > > > >=================================== >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 **********END OF ORIGINAL MESSAGE TEXT*********** George W. Durman germannaresearch@comcast.net http://trees.ancestry.com/tree/74753847
OK. This is exactly why I remain in the background. First, I was describing a scientific method for testing for a potential issue in RootsMagic. I went to a very large number and then a smaller number that would bound the potential problem to see if I could isolate the problem with a second database. And I found a similar (maybe not the same) issue and reported it. Yes, it could be that both databases have circular logic. However, scientifically, it tells me that there may also be an issue with RootsMagic. It is telling that there is a report of the issue in an early version that disappeared in a subsequent version and now has reappeared in the current version. (Not my testing but another's.) Going back to test one of the databases with the version that supposedly worked would be a validation process. For me, at this point, I don't care. Those who wish to debate genealogical research methods and motivations need to take that discussion elsewhere. This is a discussion about RootsMagic. BTW, I do not have 300 generations. I do not have 100 generations. However, my test did note a difference in the two list requests. The 300 request kept compiling for over a half hour. The 100 generation request generated an error in a much shorter time. Those are again data points for someone to look at if anyone is really interested in issues with RootsMagic. -----Original Message----- From: George W. Durman via <rootsmagic-users@rootsweb.com> To: Pat McGrath <patnbrian@charter.net>; rootsmagic-users <rootsmagic-users@rootsweb.com> Sent: Mon, May 16, 2016 11:11 pm Subject: Re: [RMagic] RM crashing in creating a large descendants list. Pat, there is no way that would be possible!!!!! 300 generations, at about 25 years per generation, would be about 7,500 years ago. Ken, have you discovered some kind of crystal ball that lets you look back that far? Why would anyone even try to do a 300, 100, 50, or 25 generation list? Utter nonsense! Yeah, I know, some "researchers" have traced their ancestors back to Adam and Eve. Don't know how many generations that would be. George At 16-05-2016 07:35 PM Monday, you wrote: *********START OF ORIGINAL MESSAGE TEXT********* >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 > > > >=================================== >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 **********END OF ORIGINAL MESSAGE TEXT*********** George W. Durman germannaresearch@comcast.net http://trees.ancestry.com/tree/74753847 =================================== 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/17/2016 8:58 AM, Kenneth Harrington via wrote: > OK. This is exactly why I remain in the background. > > First, I was describing a scientific method for testing for a potential issue in RootsMagic. I went to a very large number and then a smaller number that would bound the potential problem to see if I could isolate the problem with a second database. And I found a similar (maybe not the same) issue and reported it. > > Yes, it could be that both databases have circular logic. However, scientifically, it tells me that there may also be an issue with RootsMagic. It is telling that there is a report of the issue in an early version that disappeared in a subsequent version and now has reappeared in the current version. (Not my testing but another's.) Going back to test one of the databases with the version that supposedly worked would be a validation process. > > For me, at this point, I don't care. Those who wish to debate genealogical research methods and motivations need to take that discussion elsewhere. This is a discussion about RootsMagic. > > BTW, I do not have 300 generations. I do not have 100 generations. However, my test did note a difference in the two list requests. The 300 request kept compiling for over a half hour. The 100 generation request generated an error in a much shorter time. Those are again data points for someone to look at if anyone is really interested in issues with RootsMagic. > Ken, Sorry to have involved you in the harassment, but really appreciate your input. As an update, I've turned the "problem" over to RM support, including sending them a copy of my database so they can reproduce what I'm seeing. I'll post back here with whatever they come up with, including if it is all simply a problem with my database. > > > -----Original Message----- > <snipped> -- 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