Charlie sent me a subset of his file and I got the same sort of access violation error. I was able to stay in RM, though, getting out of the error message and able to reduce the Descendant View and use other Views. Descendant View, however, was corrupted, insofar as the border area around it gets filled to varying degrees with Red, varying with the number of generations parameter and, I think, with the number of generations actually shown. This large number of descendants stresses RM's report Previewer. Navigation to different pages of the Descendant List report was almost coffee break duration. Saving 221 pages to PDF certainly is; I'm still waiting... One CPU fully utilised - maybe it's hung? Tom -----Original Message----- From: Tom Holden Sent: Tuesday, November 20, 2012 2:10 PM To: rootsmagic-users@rootsweb.com Subject: Re: [RMagic] RootsMagic 6 Released - but still has a minor problem If you simply want someone to confirm that your data causes the problem on somebody else's computer, send me the sufficient subset. Tom On 2012-11-20, at 1:37 PM, Charlie Hoffpauir <crhoffpauir@gmail.com> wrote: > On 11/20/2012 11:06 AM, Tom Holden wrote: >> I wonder if it's an array problem. Just speculating, I have no idea how >> the Descendant view is generated. But it is clearly a bug, given that you >> can duplicate it via GEDCOM transfer. >> >> Tom > Yes. Not to wish problems on anyone else, but I kind of wish someone > else was able to duplicate the problem. If my data set is the only one > that has the problem, I doubt that it will ever be looked into by the > debuggers. And even though I doubt I'd use the Descendant list very > much, it bothers me that I have to restart RM whenever I do try to use it. >