Hi Joseph, I have a fairly large file of 468,000 names with an .fdb file of over 1.3 GB with lots of notes. My Legacy is starting to run a little slower and I'm sure that is because of the size of the file. The maximum file size is 2GB and you need some overhead. I just did a check/repair, first after several weeks. It took 5 minutes 30 seconds. A second check/repair took 3m 10s.
RAM is important for speed on a computer. I have 16GB. RAM is cheap - don't skimp. The number of processors has very little bearing on how fast the check/repair will perform particularly if you are just waiting for Legacy to finish. My computer is a 7 month old Asus with an Intel I7 CPU (with 8 processors) and Windows 10 64 bit and 16GB RAM. I partial to Intel. What to buy? My view... get a good (brand name) with lots of RAM. I like Intel over AMD and would recommend an Intel I5 (better) or I7 (best) CPU. Budget is a determining factor. I can spend 8+ hours a day on my computer (mostly on Legacy) so I want a pretty good one. Mine is classed as a 'gaming' computer but that's mostly because of the high end (4GB) video card and I don't play games! The video card won't make much difference when using Legacy. I'm now retired but have been an IT manager from before there were home computers and still help out many with computer issues. Hope this helps. Bob Austen -----Original Message----- From: LegacyUserGroup [mailto:[email protected]] On Behalf Of JV Leavitt Sent: Friday, September 29, 2017 11:43 AM To: [email protected] Subject: [LegacyUG] Check/Repair hangs on newer PCs I have a very large Legacy file of about 187,000 names, loaded up with lots of sources and notes, etc, etc. I use the latest Legacy v9 update on a Core2Duo processor running Windows 10 Home 32 bit Operating System, and 4 Gb memory, and a clock speed of 3.0 Ghz. My .fdb file is about 565Mb in size. I can run Check/Repair very reliably on this (old) system, with the Op System upgraded (downgraded really) from Win 7, but it takes about six minutes to finish. I have seen it run on a computer that was in a business environment, and it zipped through the whole thing in 3 minutes. I truly need a new computer, but I don't know what to buy, because when I run Check/Repair of my large db on any one of a number of computers that are new, with all the fastest and best features, it runs miserably slow, maybe finishing in 20 or 30 minutes, but most often hanging up completely, and never finishing (or I just didn't wait longer than that). Can anyone help me? Please, please. :-) Joseph Leavitt -- LegacyUserGroup mailing list [email protected] To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/[email protected]/ -- LegacyUserGroup mailing list [email protected] To manage your subscription and unsubscribe http://legacyusers.com/mailman/listinfo/legacyusergroup_legacyusers.com Archives at: http://www.mail-archive.com/[email protected]/
