I'm still getting the Error 91, but not permanently. The error is "error reading individual ...". Usually I can complete the backup by restarting Legacy and then immediately doing the backup.
Yesterday, though, I entered Legacy and went to the Pedigree tab to do the backup - and got the error. This morning I also got the error, from the Legacy Home tab. I do have Office 2007 on a Vista machine. But I think the problem for me started when I still had XP and Office 2000 Jack From: k...@legacyfamilytree.com [mailto:k...@legacyfamilytree.com] On Behalf Of Terri Brown Sent: 26 March 2009 01:44 To: LegacyUserGroup@legacyfamilytree.com Subject: Re: [LegacyUG] error 91 possible solution I have Office XP/2002 and get Error 91. But only with 1 file. My error 91 seems to somehow be connected to the Family tab view and families. Try doing a backup on exiting the program or from any tab EXCEPT the Family tab and you should be error-free. Also, I discovered there is more than one Error 91 message. I had been getting 2 different Error 91 messages. Fixed one. Reported my observations on the other to both support and the LUG a week or so ago. Terri _____ From: Ron Taylor <doit4...@yahoo.com> To: LegacyUserGroup@legacyfamilytree.com Sent: Wednesday, March 25, 2009 6:29:53 PM Subject: [LegacyUG] error 91 possible solution Usually, I work on my Legacy database on my old HP laptop which is running XP Pro SP3 and has an old Microsoft Office 2000 on it. I have not had any major problems with it and it does backup without error 91. Last week, I needed to merge several large files from relatives with intellishare so I put all of them on my desktop (faster computer) to do the merge. It also is running XP Pro SP3 and has Microsoft Office 2003 on it. Again, it worked well and no error 91 on backup. Then, I was using a new laptop with XP Pro SP3 and has a new Microsoft Office 2007 on it. Every time I try to do a backup...even the "Sample.fdb"...error 91. Is it possible that the new Office 2007 has introduced something which is causing the backup to fail? That is the only obvious difference. When Microsoft released Office 2007, they changed many internal features from the 97/2000/2002/2003 format. Perhaps others can comment on this possibility. Legacy users must be able to reliably backup the database without this error 91. No other enhancement or fix should take precedence over getting the backup to function again. If that means at least a warning against using Office 2007 or whatever the trigger is that causes it to crash...this has become extremely critical and needs immediate attention. Ron Taylor Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp No virus found in this incoming message. Checked by AVG - www.avg.com Version: 8.0.238 / Virus Database: 270.11.23/2016 - Release Date: 03/25/09 07:16:00 Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages: http://www.mail-archive.com/legacyusergroup@legacyfamilytree.com/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
