RE: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database
Thanks Joseph, I like your analysis! I using Win 8.1 and now realize that some 'lockups' are the computer doing something in the background without telling me. Win8 has a watchdog/auto repair mechanism and I've learned to wait out apparent lockups. Win7 may have the same. For instance, I got an error message saying there was an issue with my graphics card, not good as this is my second card, and the computer was 'locked'. I didn't (couldn't) do anything and many minutes later another message popped up to say that the repair was complete - and the computer was working again! There was no indication that the computer was functioning or doing something in the background. So, the extra 17 minutes it took to do my last Legacy check/repair was likely, as you describe, the 'processor' deciding it more urgent things to do, even though the computer, that time, was still functioning for other programs. I'm one that is sure that there is nothing wrong with the database and I'm quite sure it is not even a Legacy issue. I think it is a Win8 (and Win7 ?) 'issue'. Legacy is capable of handling large databases, but do keep those databases maintained. It would be interesting to know what OS is being used when the long delays are experienced. Of course the processor and memory are factors in 'speed' - I still have my old computer set up and it is now agonizingly slow compared to my new one. I've left the rest of the 'thread' attached. Bob A -Original Message- From: JV Leavitt [mailto:jleavi...@att.net] Sent: Saturday, July 26, 2014 1:21 PM To: legacyusergroup@LegacyUsers.com Subject: Re: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database NOTE: This was found in my Drafts folder. I just discovered I didn't send it as intended. Please excuse me for the late response. That is the same kind of thing I was experiencing with my new system. One wonders what the system was so busy with during that time. I've gone back to my old system now, which is fairly fast anyway, and am seeing only a number of relatively short stops during C/R, and it usually finishes in just over three minutes with a file of about 169,000 records. With the computer I had been using, I tried to see what the system was working on so diligently during those hangs, but it didn't seem to be doing anything that would show up on the Task Manager, or Process Explorer, or Resource Monitor, that would be considered significant -- like less than one percent activity, and nothing happening on the network either. It's as if the processor got an interrupt that told it to wait because it wanted to be ready for something really important that was going to happen, but it never does, so the processor decides, after an interminable amount of time, that it should maybe go ahead with the things it had been working on before it got the rude interrupt. I feel some doubt that there is something wrong with the database, because it causes no problem in other environments. Anyway, I find that the same thing happens with other files that have over 50,000 records, and small files never have this kind of difficulty. Joseph Leavitt On 7/22/2014 11:33 AM, Bob Austen wrote: Update... Legacy just hung up on me while doing a Check/Repair. I did several C/R's over the last two days with no problem. Today I added a number of more records and deleted a number. Ran Check/Repair and it hung up on rebuilding indexes. Oh wait, as I am writing the email it went to the next step - what was taking me under 5 minutes for the entire action took 18 minutes to get past 'Rebuilding Indexes'. (54/193) The operation completed successfully taking 22 minutes. ??? Bob A On Monday, July 21, 2014 12:42 PM, Bob Austen rgaus...@telus.net mailto:rgaus...@telus.net wrote: Joseph, As Jay points out the more memory the better. However, although it was slow, I didn't crash with a file of Jay's size on my Pentium, XP, 1GB - so you should be OK with an I5, 4GB. I have upgraded to and I7, 16GB, Win 8.1 64 bit, and it takes me about 5 minutes on a file of over 400,000 names. The time can vary depending on the number of errors found. I don't do a Check/Repair daily as Jay does - I think that's a great plan, but I get busy (lazy) and don't do it. Bob A -Original Message- From: JV Leavitt [mailto:jleavi...@att.net mailto:jleavi...@att.net] Sent: Monday, July 21, 2014 10:22 AM To: legacyusergroup@LegacyUsers.com mailto:legacyusergroup@LegacyUsers.com Subject: Re: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database Thank you Jay. I am using an I5 processor with only 4GB memory. I had a 64 bit Win 7 with 8 GB RAM installed, but since I saw the failures on other PC's like this, and that it ran fine on three separate PC's with 32 bit Win 7 and 4 GB RAM, I went to the extreme, and wrote over my 64 bit system with a 32 bit one. Now I still have
Re: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database
NOTE: This was found in my Drafts folder. I just discovered I didn't send it as intended. Please excuse me for the late response. That is the same kind of thing I was experiencing with my new system. One wonders what the system was so busy with during that time. I've gone back to my old system now, which is fairly fast anyway, and am seeing only a number of relatively short stops during C/R, and it usually finishes in just over three minutes with a file of about 169,000 records. With the computer I had been using, I tried to see what the system was working on so diligently during those hangs, but it didn't seem to be doing anything that would show up on the Task Manager, or Process Explorer, or Resource Monitor, that would be considered significant -- like less than one percent activity, and nothing happening on the network either. It's as if the processor got an interrupt that told it to wait because it wanted to be ready for something really important that was going to happen, but it never does, so the processor decides, after an interminable amount of time, that it should maybe go ahead with the things it had been working on before it got the rude interrupt. I feel some doubt that there is something wrong with the database, because it causes no problem in other environments. Anyway, I find that the same thing happens with other files that have over 50,000 records, and small files never have this kind of difficulty. Joseph Leavitt On 7/22/2014 11:33 AM, Bob Austen wrote: Update... Legacy just hung up on me while doing a Check/Repair. I did several C/R's over the last two days with no problem. Today I added a number of more records and deleted a number. Ran Check/Repair and it hung up on rebuilding indexes. Oh wait, as I am writing the email it went to the next step - what was taking me under 5 minutes for the entire action took 18 minutes to get past 'Rebuilding Indexes'. (54/193) The operation completed successfully taking 22 minutes. ??? Bob A On Monday, July 21, 2014 12:42 PM, Bob Austen rgaus...@telus.net mailto:rgaus...@telus.net wrote: Joseph, As Jay points out the more memory the better. However, although it was slow, I didn't crash with a file of Jay's size on my Pentium, XP, 1GB - so you should be OK with an I5, 4GB. I have upgraded to and I7, 16GB, Win 8.1 64 bit, and it takes me about 5 minutes on a file of over 400,000 names. The time can vary depending on the number of errors found. I don't do a Check/Repair daily as Jay does - I think that's a great plan, but I get busy (lazy) and don't do it. Bob A -Original Message- From: JV Leavitt [mailto:jleavi...@att.net mailto:jleavi...@att.net] Sent: Monday, July 21, 2014 10:22 AM To: legacyusergroup@LegacyUsers.com mailto:legacyusergroup@LegacyUsers.com Subject: Re: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database Thank you Jay. I am using an I5 processor with only 4GB memory. I had a 64 bit Win 7 with 8 GB RAM installed, but since I saw the failures on other PC's like this, and that it ran fine on three separate PC's with 32 bit Win 7 and 4 GB RAM, I went to the extreme, and wrote over my 64 bit system with a 32 bit one. Now I still have the same problem. Sigh It is very confusing because I have an older PC with a core 2 duo processor and 32 bit Win 7 and 4 GB Ram, which runs Check/Repair fine on the same database every time. It leaves me with the question as to why the same file works on some systems but not on others. The PC's at the FH Center are new I5 units with very fast processors, etc., and most but not all of them give me the same fits as I see on my new PC at home. I supposed it must be the SSD that I have on my system, but I don't think the PC's at the FH Center have SSDs, though I'm not perfectly sure about that. I am sad at having to give up my new PC and go back to my old one. However, the problem is so serious as to make it possibly the only option left. Once the Check/Repair fails, the db is ruined, and I am obliged to restore a backup file. As you can imagine, that bothers me greatly. I know I can backup, and restore the file on my wife's XP system, and then run the Check/Repair, and then..., but I don't have enough patience to do that very often. Thanks for your reply -- it does help. Joseph Leavitt On 7/21/2014 9:54 AM, Jay 1FamilyTree wrote: Joe, I run check repair once a day on my database of 230,000. If it taking as long as you say, most likely your PC needs a larger memory and a better processor. I have an I5 processor with 16GB memory, and sometimes it will take as long as 5 minutes. Try running it right after a cold startup before you open or start any other process on your PC. When I have had to troubleshoot, (Only once in over 8 years) I broke the file into two and did each one, then put them back together (I never did find the reason why, but I
RE: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database
I have Win 7 and File Check / Repair does not work on any of my files. (1200-10,000 and various sizes between) i7 processor and 8Gb memory Alan Pereira -Original Message- From: JV Leavitt [mailto:jleavi...@att.net] Sent: 21 July 2014 16:17 To: legacyusergroup@LegacyUsers.com Subject: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database Could any of you who have a very large database, like over 100,000 records, tell me if check/repair works well for you. I've seen it (on a file of 169,000 records) finish in three minutes on one system, but on my system, and a number of others I've tried, it either fails with an error, or hangs for five to fifteen minutes on various steps along the way, often hanging right away in the middle of rebuilding indexes. I have Windows 7 installed, and I've tried changing many settings and Services, and eliminating programs that might be interfering, but to no avail. Anyway, it hangs or fails the same way on many of the new computers at our local Family History Library. Any PC that has Windows XP will run Check/Repair without any problem, no matter how big the file is. I should say that I've not seen any such problem on smaller files ( I suppose under 10,000 records).. I have many small files which are the ones I usually work on, and have no difficulties with them. Any suggestions would be GREATLY appreciated. :-) Joseph Leavitt 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
Re: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database
Alan, does Check / Repair process your files okay on other computers? Does C/R just hang, or do you get an error, or do you mean it takes longer than expected? Joseph Leavitt On 7/22/2014 1:19 AM, Alan Pereira wrote: I have Win 7 and File Check / Repair does not work on any of my files. (1200-10,000 and various sizes between) i7 processor and 8Gb memory Alan Pereira -Original Message- From: JV Leavitt [mailto:jleavi...@att.net] Sent: 21 July 2014 16:17 To: legacyusergroup@LegacyUsers.com Subject: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database Could any of you who have a very large database, like over 100,000 records, tell me if check/repair works well for you. I've seen it (on a file of 169,000 records) finish in three minutes on one system, but on my system, and a number of others I've tried, it either fails with an error, or hangs for five to fifteen minutes on various steps along the way, often hanging right away in the middle of rebuilding indexes. I have Windows 7 installed, and I've tried changing many settings and Services, and eliminating programs that might be interfering, but to no avail. Anyway, it hangs or fails the same way on many of the new computers at our local Family History Library. Any PC that has Windows XP will run Check/Repair without any problem, no matter how big the file is. I should say that I've not seen any such problem on smaller files ( I suppose under 10,000 records).. I have many small files which are the ones I usually work on, and have no difficulties with them. Any suggestions would be GREATLY appreciated. :-) Joseph Leavitt 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
RE: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database
Joseph, It just sat there with the win 7 circle revolving and doing nothing. I cancelled, tried another 2 fdb files with the same result. I rebooted the machine and it all worked fine. I am not in the habit of leaving my machine on but must have done something before opening Legacy that caused this behaviour. I can't repeat the problem. Alan -Original Message- From: JV Leavitt [mailto:jleavi...@att.net] Sent: 22 July 2014 14:55 To: legacyusergroup@LegacyUsers.com Subject: Re: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database Alan, does Check / Repair process your files okay on other computers? Does C/R just hang, or do you get an error, or do you mean it takes longer than expected? Joseph Leavitt On 7/22/2014 1:19 AM, Alan Pereira wrote: I have Win 7 and File Check / Repair does not work on any of my files. (1200-10,000 and various sizes between) i7 processor and 8Gb memory Alan Pereira -Original Message- From: JV Leavitt [mailto:jleavi...@att.net] Sent: 21 July 2014 16:17 To: legacyusergroup@LegacyUsers.com Subject: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database Could any of you who have a very large database, like over 100,000 records, tell me if check/repair works well for you. I've seen it (on a file of 169,000 records) finish in three minutes on one system, but on my system, and a number of others I've tried, it either fails with an error, or hangs for five to fifteen minutes on various steps along the way, often hanging right away in the middle of rebuilding indexes. I have Windows 7 installed, and I've tried changing many settings and Services, and eliminating programs that might be interfering, but to no avail. Anyway, it hangs or fails the same way on many of the new computers at our local Family History Library. Any PC that has Windows XP will run Check/Repair without any problem, no matter how big the file is. I should say that I've not seen any such problem on smaller files ( I suppose under 10,000 records).. I have many small files which are the ones I usually work on, and have no difficulties with them. Any suggestions would be GREATLY appreciated. :-) Joseph Leavitt 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 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
Re: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database
Whew! Good thinking. Power-on-reset, a term I used in my old profession, has fixed a multitude of problems, over the years. :-) Joseph Leavitt On 7/22/2014 7:38 AM, Alan Pereira wrote: Joseph, It just sat there with the win 7 circle revolving and doing nothing. I cancelled, tried another 2 fdb files with the same result. I rebooted the machine and it all worked fine. I am not in the habit of leaving my machine on but must have done something before opening Legacy that caused this behaviour. I can't repeat the problem. Alan -Original Message- From: JV Leavitt [mailto:jleavi...@att.net] Sent: 22 July 2014 14:55 To: legacyusergroup@LegacyUsers.com Subject: Re: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database Alan, does Check / Repair process your files okay on other computers? Does C/R just hang, or do you get an error, or do you mean it takes longer than expected? Joseph Leavitt On 7/22/2014 1:19 AM, Alan Pereira wrote: I have Win 7 and File Check / Repair does not work on any of my files. (1200-10,000 and various sizes between) i7 processor and 8Gb memory Alan Pereira -Original Message- From: JV Leavitt [mailto:jleavi...@att.net] Sent: 21 July 2014 16:17 To: legacyusergroup@LegacyUsers.com Subject: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database Could any of you who have a very large database, like over 100,000 records, tell me if check/repair works well for you. I've seen it (on a file of 169,000 records) finish in three minutes on one system, but on my system, and a number of others I've tried, it either fails with an error, or hangs for five to fifteen minutes on various steps along the way, often hanging right away in the middle of rebuilding indexes. I have Windows 7 installed, and I've tried changing many settings and Services, and eliminating programs that might be interfering, but to no avail. Anyway, it hangs or fails the same way on many of the new computers at our local Family History Library. Any PC that has Windows XP will run Check/Repair without any problem, no matter how big the file is. I should say that I've not seen any such problem on smaller files ( I suppose under 10,000 records).. I have many small files which are the ones I usually work on, and have no difficulties with them. Any suggestions would be GREATLY appreciated. :-) Joseph Leavitt 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 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 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
Re: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database
Shut down, restart even worked for a copy (Xerox?) machine about 1965. Jay Ingalls = On 7/22/2014 9:51 AM, JV Leavitt wrote: Whew! Good thinking. Power-on-reset, a term I used in my old profession, has fixed a multitude of problems, over the years. :-) Joseph Leavitt On 7/22/2014 7:38 AM, Alan Pereira wrote: Joseph, It just sat there with the win 7 circle revolving and doing nothing. I cancelled, tried another 2 fdb files with the same result. I rebooted the machine and it all worked fine. I am not in the habit of leaving my machine on but must have done something before opening Legacy that caused this behaviour. I can't repeat the problem. Alan -Original Message- From: JV Leavitt [mailto:jleavi...@att.net] Sent: 22 July 2014 14:55 To: legacyusergroup@LegacyUsers.com Subject: Re: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database Alan, does Check / Repair process your files okay on other computers? Does C/R just hang, or do you get an error, or do you mean it takes longer than expected? Joseph Leavitt On 7/22/2014 1:19 AM, Alan Pereira wrote: I have Win 7 and File Check / Repair does not work on any of my files. (1200-10,000 and various sizes between) i7 processor and 8Gb memory Alan Pereira -Original Message- From: JV Leavitt [mailto:jleavi...@att.net] Sent: 21 July 2014 16:17 To: legacyusergroup@LegacyUsers.com Subject: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database Could any of you who have a very large database, like over 100,000 records, tell me if check/repair works well for you. I've seen it (on a file of 169,000 records) finish in three minutes on one system, but on my system, and a number of others I've tried, it either fails with an error, or hangs for five to fifteen minutes on various steps along the way, often hanging right away in the middle of rebuilding indexes. I have Windows 7 installed, and I've tried changing many settings and Services, and eliminating programs that might be interfering, but to no avail. Anyway, it hangs or fails the same way on many of the new computers at our local Family History Library. Any PC that has Windows XP will run Check/Repair without any problem, no matter how big the file is. I should say that I've not seen any such problem on smaller files ( I suppose under 10,000 records).. I have many small files which are the ones I usually work on, and have no difficulties with them. Any suggestions would be GREATLY appreciated. :-) Joseph Leavitt 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 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 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 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
RE: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database
Update... Legacy just hung up on me while doing a Check/Repair. I did several C/R's over the last two days with no problem. Today I added a number of more records and deleted a number. Ran Check/Repair and it hung up on rebuilding indexes. Oh wait, as I am writing the email it went to the next step - what was taking me under 5 minutes for the entire action took 18 minutes to get past 'Rebuilding Indexes'. (54/193) The operation completed successfully taking 22 minutes. ??? Bob A On Monday, July 21, 2014 12:42 PM, Bob Austen rgaus...@telus.net wrote: Joseph, As Jay points out the more memory the better. However, although it was slow, I didn't crash with a file of Jay's size on my Pentium, XP, 1GB - so you should be OK with an I5, 4GB. I have upgraded to and I7, 16GB, Win 8.1 64 bit, and it takes me about 5 minutes on a file of over 400,000 names. The time can vary depending on the number of errors found. I don't do a Check/Repair daily as Jay does - I think that's a great plan, but I get busy (lazy) and don't do it. Bob A -Original Message- From: JV Leavitt [mailto:jleavi...@att.net] Sent: Monday, July 21, 2014 10:22 AM To: legacyusergroup@LegacyUsers.com Subject: Re: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database Thank you Jay. I am using an I5 processor with only 4GB memory. I had a 64 bit Win 7 with 8 GB RAM installed, but since I saw the failures on other PC's like this, and that it ran fine on three separate PC's with 32 bit Win 7 and 4 GB RAM, I went to the extreme, and wrote over my 64 bit system with a 32 bit one. Now I still have the same problem. Sigh It is very confusing because I have an older PC with a core 2 duo processor and 32 bit Win 7 and 4 GB Ram, which runs Check/Repair fine on the same database every time. It leaves me with the question as to why the same file works on some systems but not on others. The PC's at the FH Center are new I5 units with very fast processors, etc., and most but not all of them give me the same fits as I see on my new PC at home. I supposed it must be the SSD that I have on my system, but I don't think the PC's at the FH Center have SSDs, though I'm not perfectly sure about that. I am sad at having to give up my new PC and go back to my old one. However, the problem is so serious as to make it possibly the only option left. Once the Check/Repair fails, the db is ruined, and I am obliged to restore a backup file. As you can imagine, that bothers me greatly. I know I can backup, and restore the file on my wife's XP system, and then run the Check/Repair, and then..., but I don't have enough patience to do that very often. Thanks for your reply -- it does help. Joseph Leavitt On 7/21/2014 9:54 AM, Jay 1FamilyTree wrote: Joe, I run check repair once a day on my database of 230,000. If it taking as long as you say, most likely your PC needs a larger memory and a better processor. I have an I5 processor with 16GB memory, and sometimes it will take as long as 5 minutes. Try running it right after a cold startup before you open or start any other process on your PC. When I have had to troubleshoot, (Only once in over 8 years) I broke the file into two and did each one, then put them back together (I never did find the reason why, but I didnt care as my data was safe and correct.) Hope that helps, Jay On Mon, Jul 21, 2014 at 8:16 AM, JV Leavitt jleavi...@att.net mailto:jleavi...@att.net wrote: Could any of you who have a very large database, like over 100,000 records, tell me if check/repair works well for you. I've seen it (on a file of 169,000 records) finish in three minutes on one system, but on my system, and a number of others I've tried, it either fails with an error, or hangs for five to fifteen minutes on various steps along the way, often hanging right away in the middle of rebuilding indexes. I have Windows 7 installed, and I've tried changing many settings and Services, and eliminating programs that might be interfering, but to no avail. Anyway, it hangs or fails the same way on many of the new computers at our local Family History Library. Any PC that has Windows XP will run Check/Repair without any problem, no matter how big the file is. I should say that I've not seen any such problem on smaller files ( I suppose under 10,000 records).. I have many small files which are the ones I usually work on, and have no difficulties with them. Any suggestions would be GREATLY appreciated. :-) Joseph Leavitt 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
Re: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database
If that is the case I would be seriously worried. In effect, if File check is not completing. then your database integrity in not reliable. And the possibility exists that you data will be compromised. I hope you find a solution soon. It would be a shame to lose all your hard work. On Tue, Jul 22, 2014 at 1:19 AM, Alan Pereira alanpere...@tiscali.co.uk wrote: I have Win 7 and File Check / Repair does not work on any of my files. (1200-10,000 and various sizes between) i7 processor and 8Gb memory Alan Pereira -Original Message- From: JV Leavitt [mailto:jleavi...@att.net] Sent: 21 July 2014 16:17 To: legacyusergroup@LegacyUsers.com Subject: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database Could any of you who have a very large database, like over 100,000 records, tell me if check/repair works well for you. I've seen it (on a file of 169,000 records) finish in three minutes on one system, but on my system, and a number of others I've tried, it either fails with an error, or hangs for five to fifteen minutes on various steps along the way, often hanging right away in the middle of rebuilding indexes. I have Windows 7 installed, and I've tried changing many settings and Services, and eliminating programs that might be interfering, but to no avail. Anyway, it hangs or fails the same way on many of the new computers at our local Family History Library. Any PC that has Windows XP will run Check/Repair without any problem, no matter how big the file is. I should say that I've not seen any such problem on smaller files ( I suppose under 10,000 records).. I have many small files which are the ones I usually work on, and have no difficulties with them. Any suggestions would be GREATLY appreciated. :-) Joseph Leavitt 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 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
Re: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database
And if it doesn't, don't turn it back on so fast next time. :) Cheryl Singhal J.M. Jay Ingalls wrote: Shut down, restart even worked for a copy (Xerox?) machine about 1965. Jay Ingalls = On 7/22/2014 9:51 AM, JV Leavitt wrote: Whew! Good thinking. Power-on-reset, a term I used in my old profession, has fixed a multitude of problems, over the years. :-) Joseph Leavitt On 7/22/2014 7:38 AM, Alan Pereira wrote: Joseph, It just sat there with the win 7 circle revolving and doing nothing. I cancelled, tried another 2 fdb files with the same result. I rebooted the machine and it all worked fine. I am not in the habit of leaving my machine on but must have done something before opening Legacy that caused this behaviour. I can't repeat the problem. Alan -Original Message- From: JV Leavitt [mailto:jleavi...@att.net] Sent: 22 July 2014 14:55 To: legacyusergroup@LegacyUsers.com Subject: Re: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database Alan, does Check / Repair process your files okay on other computers? Does C/R just hang, or do you get an error, or do you mean it takes longer than expected? Joseph Leavitt On 7/22/2014 1:19 AM, Alan Pereira wrote: I have Win 7 and File Check / Repair does not work on any of my files. (1200-10,000 and various sizes between) i7 processor and 8Gb memory Alan Pereira -Original Message- From: JV Leavitt [mailto:jleavi...@att.net] Sent: 21 July 2014 16:17 To: legacyusergroup@LegacyUsers.com Subject: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database Could any of you who have a very large database, like over 100,000 records, tell me if check/repair works well for you. I've seen it (on a file of 169,000 records) finish in three minutes on one system, but on my system, and a number of others I've tried, it either fails with an error, or hangs for five to fifteen minutes on various steps along the way, often hanging right away in the middle of rebuilding indexes. I have Windows 7 installed, and I've tried changing many settings and Services, and eliminating programs that might be interfering, but to no avail. Anyway, it hangs or fails the same way on many of the new computers at our local Family History Library. Any PC that has Windows XP will run Check/Repair without any problem, no matter how big the file is. I should say that I've not seen any such problem on smaller files ( I suppose under 10,000 records).. I have many small files which are the ones I usually work on, and have no difficulties with them. Any suggestions would be GREATLY appreciated. :-) Joseph Leavitt 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
[LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database
Could any of you who have a very large database, like over 100,000 records, tell me if check/repair works well for you. I've seen it (on a file of 169,000 records) finish in three minutes on one system, but on my system, and a number of others I've tried, it either fails with an error, or hangs for five to fifteen minutes on various steps along the way, often hanging right away in the middle of rebuilding indexes. I have Windows 7 installed, and I've tried changing many settings and Services, and eliminating programs that might be interfering, but to no avail. Anyway, it hangs or fails the same way on many of the new computers at our local Family History Library. Any PC that has Windows XP will run Check/Repair without any problem, no matter how big the file is. I should say that I've not seen any such problem on smaller files ( I suppose under 10,000 records).. I have many small files which are the ones I usually work on, and have no difficulties with them. Any suggestions would be GREATLY appreciated. :-) Joseph Leavitt 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
Re: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database
Joe, I run check repair once a day on my database of 230,000. If it taking as long as you say, most likely your PC needs a larger memory and a better processor. I have an I5 processor with 16GB memory, and sometimes it will take as long as 5 minutes. Try running it right after a cold startup before you open or start any other process on your PC. When I have had to troubleshoot, (Only once in over 8 years) I broke the file into two and did each one, then put them back together (I never did find the reason why, but I didnt care as my data was safe and correct.) Hope that helps, Jay On Mon, Jul 21, 2014 at 8:16 AM, JV Leavitt jleavi...@att.net wrote: Could any of you who have a very large database, like over 100,000 records, tell me if check/repair works well for you. I've seen it (on a file of 169,000 records) finish in three minutes on one system, but on my system, and a number of others I've tried, it either fails with an error, or hangs for five to fifteen minutes on various steps along the way, often hanging right away in the middle of rebuilding indexes. I have Windows 7 installed, and I've tried changing many settings and Services, and eliminating programs that might be interfering, but to no avail. Anyway, it hangs or fails the same way on many of the new computers at our local Family History Library. Any PC that has Windows XP will run Check/Repair without any problem, no matter how big the file is. I should say that I've not seen any such problem on smaller files ( I suppose under 10,000 records).. I have many small files which are the ones I usually work on, and have no difficulties with them. Any suggestions would be GREATLY appreciated. :-) Joseph Leavitt 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 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
Re: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database
Thank you Jay. I am using an I5 processor with only 4GB memory. I had a 64 bit Win 7 with 8 GB RAM installed, but since I saw the failures on other PC's like this, and that it ran fine on three separate PC's with 32 bit Win 7 and 4 GB RAM, I went to the extreme, and wrote over my 64 bit system with a 32 bit one. Now I still have the same problem. Sigh It is very confusing because I have an older PC with a core 2 duo processor and 32 bit Win 7 and 4 GB Ram, which runs Check/Repair fine on the same database every time. It leaves me with the question as to why the same file works on some systems but not on others. The PC's at the FH Center are new I5 units with very fast processors, etc., and most but not all of them give me the same fits as I see on my new PC at home. I supposed it must be the SSD that I have on my system, but I don't think the PC's at the FH Center have SSDs, though I'm not perfectly sure about that. I am sad at having to give up my new PC and go back to my old one. However, the problem is so serious as to make it possibly the only option left. Once the Check/Repair fails, the db is ruined, and I am obliged to restore a backup file. As you can imagine, that bothers me greatly. I know I can backup, and restore the file on my wife's XP system, and then run the Check/Repair, and then..., but I don't have enough patience to do that very often. Thanks for your reply -- it does help. Joseph Leavitt On 7/21/2014 9:54 AM, Jay 1FamilyTree wrote: Joe, I run check repair once a day on my database of 230,000. If it taking as long as you say, most likely your PC needs a larger memory and a better processor. I have an I5 processor with 16GB memory, and sometimes it will take as long as 5 minutes. Try running it right after a cold startup before you open or start any other process on your PC. When I have had to troubleshoot, (Only once in over 8 years) I broke the file into two and did each one, then put them back together (I never did find the reason why, but I didnt care as my data was safe and correct.) Hope that helps, Jay On Mon, Jul 21, 2014 at 8:16 AM, JV Leavitt jleavi...@att.net mailto:jleavi...@att.net wrote: Could any of you who have a very large database, like over 100,000 records, tell me if check/repair works well for you. I've seen it (on a file of 169,000 records) finish in three minutes on one system, but on my system, and a number of others I've tried, it either fails with an error, or hangs for five to fifteen minutes on various steps along the way, often hanging right away in the middle of rebuilding indexes. I have Windows 7 installed, and I've tried changing many settings and Services, and eliminating programs that might be interfering, but to no avail. Anyway, it hangs or fails the same way on many of the new computers at our local Family History Library. Any PC that has Windows XP will run Check/Repair without any problem, no matter how big the file is. I should say that I've not seen any such problem on smaller files ( I suppose under 10,000 records).. I have many small files which are the ones I usually work on, and have no difficulties with them. Any suggestions would be GREATLY appreciated. :-) Joseph Leavitt 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 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 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
Re: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database
Joseph, I would also suggest you try two things; First, run your gedcom thru several of the Gedcom checkers out there to find any potential errors like bad dates that may be causing the hiccups and problems. I like the Genealogy Grafica for its speed, and Bonkers for 'sanity' tho' you might have to send an email to Tim with ur gedcom because of the size. Second, If you dont already own LTools (I think its still under $20) you can use that to open the tables in your database and just visually review them for any 'bad data' that might stand out. Tedious and time consuming, but it is an affordable method that may find a problem. Lastly, Maybe a formal support request to Legacy and ask them to run it and what their results are? Best of Luck Jay On Mon, Jul 21, 2014 at 10:21 AM, JV Leavitt jleavi...@att.net wrote: Thank you Jay. I am using an I5 processor with only 4GB memory. I had a 64 bit Win 7 with 8 GB RAM installed, but since I saw the failures on other PC's like this, and that it ran fine on three separate PC's with 32 bit Win 7 and 4 GB RAM, I went to the extreme, and wrote over my 64 bit system with a 32 bit one. Now I still have the same problem. Sigh It is very confusing because I have an older PC with a core 2 duo processor and 32 bit Win 7 and 4 GB Ram, which runs Check/Repair fine on the same database every time. It leaves me with the question as to why the same file works on some systems but not on others. The PC's at the FH Center are new I5 units with very fast processors, etc., and most but not all of them give me the same fits as I see on my new PC at home. I supposed it must be the SSD that I have on my system, but I don't think the PC's at the FH Center have SSDs, though I'm not perfectly sure about that. I am sad at having to give up my new PC and go back to my old one. However, the problem is so serious as to make it possibly the only option left. Once the Check/Repair fails, the db is ruined, and I am obliged to restore a backup file. As you can imagine, that bothers me greatly. I know I can backup, and restore the file on my wife's XP system, and then run the Check/Repair, and then..., but I don't have enough patience to do that very often. Thanks for your reply -- it does help. Joseph Leavitt On 7/21/2014 9:54 AM, Jay 1FamilyTree wrote: Joe, I run check repair once a day on my database of 230,000. If it taking as long as you say, most likely your PC needs a larger memory and a better processor. I have an I5 processor with 16GB memory, and sometimes it will take as long as 5 minutes. Try running it right after a cold startup before you open or start any other process on your PC. When I have had to troubleshoot, (Only once in over 8 years) I broke the file into two and did each one, then put them back together (I never did find the reason why, but I didnt care as my data was safe and correct.) Hope that helps, Jay On Mon, Jul 21, 2014 at 8:16 AM, JV Leavitt jleavi...@att.net mailto:jleavi...@att.net wrote: Could any of you who have a very large database, like over 100,000 records, tell me if check/repair works well for you. I've seen it (on a file of 169,000 records) finish in three minutes on one system, but on my system, and a number of others I've tried, it either fails with an error, or hangs for five to fifteen minutes on various steps along the way, often hanging right away in the middle of rebuilding indexes. I have Windows 7 installed, and I've tried changing many settings and Services, and eliminating programs that might be interfering, but to no avail. Anyway, it hangs or fails the same way on many of the new computers at our local Family History Library. Any PC that has Windows XP will run Check/Repair without any problem, no matter how big the file is. I should say that I've not seen any such problem on smaller files ( I suppose under 10,000 records).. I have many small files which are the ones I usually work on, and have no difficulties with them. Any suggestions would be GREATLY appreciated. :-) Joseph Leavitt 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 Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp
RE: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database
Joseph, As Jay points out the more memory the better. However, although it was slow, I didn't crash with a file of Jay's size on my Pentium, XP, 1GB - so you should be OK with an I5, 4GB. I have upgraded to and I7, 16GB, Win 8.1 64 bit, and it takes me about 5 minutes on a file of over 400,000 names. The time can vary depending on the number of errors found. I don't do a Check/Repair daily as Jay does - I think that's a great plan, but I get busy (lazy) and don't do it. Bob A -Original Message- From: JV Leavitt [mailto:jleavi...@att.net] Sent: Monday, July 21, 2014 10:22 AM To: legacyusergroup@LegacyUsers.com Subject: Re: [LegacyUG] Legacy v8 any build - Windows 7 -- Check/Repair on large database Thank you Jay. I am using an I5 processor with only 4GB memory. I had a 64 bit Win 7 with 8 GB RAM installed, but since I saw the failures on other PC's like this, and that it ran fine on three separate PC's with 32 bit Win 7 and 4 GB RAM, I went to the extreme, and wrote over my 64 bit system with a 32 bit one. Now I still have the same problem. Sigh It is very confusing because I have an older PC with a core 2 duo processor and 32 bit Win 7 and 4 GB Ram, which runs Check/Repair fine on the same database every time. It leaves me with the question as to why the same file works on some systems but not on others. The PC's at the FH Center are new I5 units with very fast processors, etc., and most but not all of them give me the same fits as I see on my new PC at home. I supposed it must be the SSD that I have on my system, but I don't think the PC's at the FH Center have SSDs, though I'm not perfectly sure about that. I am sad at having to give up my new PC and go back to my old one. However, the problem is so serious as to make it possibly the only option left. Once the Check/Repair fails, the db is ruined, and I am obliged to restore a backup file. As you can imagine, that bothers me greatly. I know I can backup, and restore the file on my wife's XP system, and then run the Check/Repair, and then..., but I don't have enough patience to do that very often. Thanks for your reply -- it does help. Joseph Leavitt On 7/21/2014 9:54 AM, Jay 1FamilyTree wrote: Joe, I run check repair once a day on my database of 230,000. If it taking as long as you say, most likely your PC needs a larger memory and a better processor. I have an I5 processor with 16GB memory, and sometimes it will take as long as 5 minutes. Try running it right after a cold startup before you open or start any other process on your PC. When I have had to troubleshoot, (Only once in over 8 years) I broke the file into two and did each one, then put them back together (I never did find the reason why, but I didnt care as my data was safe and correct.) Hope that helps, Jay On Mon, Jul 21, 2014 at 8:16 AM, JV Leavitt jleavi...@att.net mailto:jleavi...@att.net wrote: Could any of you who have a very large database, like over 100,000 records, tell me if check/repair works well for you. I've seen it (on a file of 169,000 records) finish in three minutes on one system, but on my system, and a number of others I've tried, it either fails with an error, or hangs for five to fifteen minutes on various steps along the way, often hanging right away in the middle of rebuilding indexes. I have Windows 7 installed, and I've tried changing many settings and Services, and eliminating programs that might be interfering, but to no avail. Anyway, it hangs or fails the same way on many of the new computers at our local Family History Library. Any PC that has Windows XP will run Check/Repair without any problem, no matter how big the file is. I should say that I've not seen any such problem on smaller files ( I suppose under 10,000 records).. I have many small files which are the ones I usually work on, and have no difficulties with them. Any suggestions would be GREATLY appreciated. :-) Joseph Leavitt 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
