Guy R Spangler <grspangler@ualr.edu> wrote: >When I create a book, >I see a male Spangler as the first entry for each generation. >For my girls, I'd like to create a book with their mother, and >all her children, next generation her mother, next generation >her mother... Like that. An ancestor book is patterned after the ahnentafel pedigree chart with the father in the top of the bracket and the mother in the bottom. The ahnentafel numbers follow this form and not much can be done about that. In a descendant book the first entry in each generation is the ancestor from that generation. Sometimes it is a male, sometimes it is a female. If you want the male ancestor's wife to be the first person listed, you can do a one generation descendant book of her. You can do a one generation descendant book for each generation, always of the female spouse, send them all to RTF files, and collect them all together into one document and thereby construct a book such as you want. In FO10, using the new journal feature, you will be able to make all these one-generation descendant books and have FO10 collect them all together into one single journal book report and provide a common index for the whole works. You still might want to send it to an RTF file, for the various one-generation sections will all say "first generation" and you might want to edit that. (You will also be able to have FO10 send the whole journal report to a PDF acrobat file, too) Wayne League

Dear Friends Since v6 I've had absolutely no problems with FO, but now a strange one has cropped up. Whenever I try to export to a GEDCOM, FO stops after processing about 400 entries into my 17,000 person database, and gives the error message: Error #: -902 Error #: 95909 Out of Memory u4allocErDefault FO then aborts. (This doesn't happen when I try to back up.) I first restored my recent backup and tried again. Same problem. Since then, I've completely re-installed FO and checked my memory allocation (I have 128 megs of RAM) but nothing seems to make a difference. I've been running FO on this same computer for nearly two years without a hitch. Any ideas? I use the export to GEDCOM function a lot and am worried that something further will now go wrong. Version 10 should arrive in the mail soon, but I still want to fix this problem! Thanks in advance. Patrick ----------------- Patrick McDonald PO Box 357 Round Corner, NSW 2158 AUSTRALIA Fax +61-2-9651-3778 patrick@mpx.com.au patrick@aussiehobbies.com.au

"Patrick McDonald" <patrick@aussiehobbies.com.au> wrote: >Whenever I try to export to a GEDCOM, FO stops after processing about 400 >entries into my 17,000 person database, and gives the error message: In older versions of FO this would be caused by having a long line with no spaces in it in a source or in a note. A line such as a long URL to a website or a dividing line in a note like this: =================================================================================== Breaking the line up with spaces would solve the hang-up problem. This problem has been fixed in the later versions of FO. There have been a few other irregularities that would cause a gedcom export or import to hang the computer, but I don't remember what all they were. If you can't find a long line then you might try finding that 17000th person where the hangup occurs. You know you've found the right one if you leave him out of the gedcom export and then the gedcom exports OK. If you can't see anything unusual about his entry then you might just delete him completely and re-enter him. That would fix an unseen irregularity. Wayne League

Dear Wayne Thanks for your reply. I think you may have put your finger exactly on the problem, because the trouble started when I was editing a very long note on my of my entries. This entry also included a long ========= dividing two parts of the note. And the note was about entry no. 400 in my database, which is where the GEDCOM export stopped each time. As you may have already read, I received a tip from Ron, and when I went back and restored from an earlier back-up (but not the most recent), the problem disappeared. Anyhow, I will certainly know what to do if I encounter this error message again. BTW, I am using v9.02 so the problem obviously occurs in newer versions of FO. Thanks again for your help! Patrick ----------------- Patrick McDonald PO Box 357 Round Corner, NSW 2158 AUSTRALIA Fax +61-2-9651-3778 patrick@mpx.com.au patrick@aussiehobbies.com.au ----- Original Message ----- From: "Wayne League" <wleague@mindspring.com> To: <FAMILY-ORIGINS-USERS-L@rootsweb.com> Sent: Saturday, August 25, 2001 4:08 AM Subject: Re: [FO] Strange FO Error Message -- Please Help! > "Patrick McDonald" <patrick@aussiehobbies.com.au> wrote: > > >Whenever I try to export to a GEDCOM, FO stops after processing about 400 > >entries into my 17,000 person database, and gives the error message: > > In older versions of FO this would be caused by having a long line > with no spaces in it in a source or in a note. A line such as a long > URL to a website or a dividing line in a note like this: > ============================================================================ ======= > > Breaking the line up with spaces would solve the hang-up problem. > This problem has been fixed in the later versions of FO. > > There have been a few other irregularities that would cause a gedcom > export or import to hang the computer, but I don't remember what all > they were. > If you can't find a long line then you might try finding that 17000th > person where the hangup occurs. You know you've found the right one > if you leave him out of the gedcom export and then the gedcom exports > OK. If you can't see anything unusual about his entry then you might > just delete him completely and re-enter him. That would fix an unseen > irregularity. > > Wayne League

Dear Ron Thanks for your very quick reply. I appreciate it and it pointed me in the right direction. Assuming that I was facing a corrupted data entry situation, I went back to my *second-last* backup, restored that, and all was well. I had a moderate amount of new data to key in again, but it was worth it. I wonder why it happened? Anyhow, I've ordered v10 and will look forward to trying it out after it completes the long trip across the Pacific. Best wishes Patrick