Ellen, I suggest that you follow the advice to send the file to Ken, and then follow their advice re: reinstalling Legacy, or whatever. I have no doubt that it is corrupt.
Legacy runs OK on both 32 and 64bit - I am using a Win7 64bit machine. But if you go this route do ensure that your file has been repaired before attempting to run it. Ron Ferguson http://www.fergys.co.uk/ -----Original Message----- From: Ellen Sent: Sunday, June 17, 2012 10:28 PM To: LegacyUserGroup@LegacyUsers.com Subject: Re: [LegacyUG] Error 3800 and other problems Would a new computer help? Does it matter if it is 64 bit or 32 bit? I also got a message to send the file to Ken@Legacy... Did the emails on printing reports deal with not being able to save reports in .rtf and .pdf? That is another thing that I am dealing with. God bless, Ellen On Jun 17, 2012, at 5:17 PM, Ellen wrote: > I have no idea how to export or what a 5.5 standard might be. > God bless, > Ellen > > On Jun 17, 2012, at 4:44 PM, Tim Rosenlof wrote: > >> On 6/17/2012 2:32 PM, Jenny M Benson wrote: >>> On 17/06/2012 20:48, Ellen wrote: >>>> Dear people: >>>> >>>> I am able to do many things on computers but I am at my wits end with >>>> these issues. >>>> >>>> 1) I am getting error messages about Error 3800. Somehow I cannot >>>> figure this out even though I looked at the website. I must be >>>> totally flustered because >>>> >>>> 2) I cannot get any reports to save or print from Legacy. It was >>>> saving everything in rt1 or rf1 and not rtf or pdf. >>>> >>>> I also got some erorr about a baptism file not being available so I >>>> did an update of Legacy. I was trying not to update till after our >>>> book is done, but relatives are trying to help proofread this massive >>>> series of books and I cannot get it working. I did check repair >>>> numbers of times and it still is not working. PLeeeeeeease help. >>>> When these error messages come up, the only option that I have that >>>> works is to quit Legacy. >>>> >>>> Now I have Error 3426 coming up too. >>> Are you using the latest verion of Legacy? If not, update. >>> >>> When you did Check & Repair was it finding any errors? If so, did you >>> correct the errors and repeat until none were found? If not, do that. >>> >>> Try exporting your family file to one with a new name and see if that >>> will run correctly. >>> >>> If that fails, try re-installing Legacy. (Make sure you keep your >>> family file and, for double safety's sake, a backup .) >> >> I think your advice to try exporting then importing is great. That is >> what I would do if it was happening to me. Be careful not to export to a >> 5.5 standard because if you have SourceWriter, your sources will revert >> to basic. >> >> -- >> Tim Rosenlof >> Utah, USA >> Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyusers.com/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
