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 > > 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
