Perhaps it is a “bad sector” on your computer’s hard disk? I would scan the disk using Windows – File Explorer, select the C: Drive (that is where most Legacy things are hosted), right click, select Properties (bottom item in the menu), Tools (tab), and click the Check button. It is unlikely that the .fdb file would be larger than 2GB – but after in Legacy - backup, check/repair – I sometimes also select Compact file.
Ian Albert Park, Victoria 3206 Australia From: LegacyUserGroup [mailto:[email protected]] On Behalf Of Chris Hill Sent: Monday, 7 October 2019 10:15 PM To: Legacy User Group <[email protected]> Subject: Re: [LegacyUG] Error 3035 during Check-Repair Build 9.0.0.318 Hi Legacy support site says We are uncertain as to the causes of "3035: System resource exceeded", which is not that useful. However, there are known issues with Access, which Legacy uses for its database, relating to 'System resource exceeded'. One limitation is the size, physical, of the .fdb files, which must not exceed 2GB, but would probably error if somewhat smaller. I have also seen a fix which involved limiting the number of CPUs that Access is using, but I am not aware if that relates to the Legacy app or an imbedded part of the system. Part of the problem is that the causes are variable which makes it difficult to resolve. Regards Chris ------ Original Message ------ From: "Alan Thompson" <[email protected]<mailto:[email protected]>> To: [email protected]<mailto:[email protected]> Sent: 07/10/2019 10:02:50 Subject: [LegacyUG] Error 3035 during Check-Repair Build 9.0.0.318 Has anyone else had problems with the Check-Repair routine using the latest release Legacy 9.0 Build 318. I repeatedly get a “ Run Time Error ‘3035 System resource exceeded “message at Step 65 of 219 of Check-Repair and was wondering if anyone else was experiencing similar. I tried uninstalling Legacy and re-installing (as recommended for this error message) and running check-repair on the same Family file but again received the same error message. I also tried exporting my family file to a new Legacy database and running Check-Repair on that, again without success. However, on a different computer (with less resources, ie CPU and Memory, but with the same version of Windows 10 with latest updates), I ran check-repair using Legacy Version 9.0.0.301 (ie the previous release) on the same family files (as above) and check-repair completed successfully in both cases. Also restored a back-up of my family file taken immediately prior to updating to Build 9.0.0.318. Running check repair on this file using Version 9.0.0.318 again failed at the same point, but successfully completed using 9.0.0.301. My Family File details: Number of Individuals: 143931 Number of Families: 44941 Master locations: 20761 Master Sources: 1245 Citations: 759965 Master events: 197212 used by individuals: 196591 used by marriages: 621 Master media items: 73894 times linked: 303918 I have reported this problem to support. Alan Thompson Canberra, Australia
-- 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]/
