I found this old code, not sure if it will help your problem? ***to repair hsaudit.dbf close all set exclusive off set TABLEVALIDATE to 0 select 0 use hsaudit.dbf wait "Please be patient, step 1 of 2. Copying hsaudit table to temporary table..." window at 25,50 nowait copy to hstemp with cdx select hsaudit use in hsaudit wait "Please be patient, step 2 of 2. Copying temporary table to hsaudit table..." window at 25,50 nowait copy file hstemp.* to hsaudit.* wait clear select 0 use hsaudit browse noedit
James E Harvey Hanover Shoe Farms, Inc. M.I.S./Corresponding Officer Off: 717-637-8931 fax: 717-637-6766 email: [email protected] -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of John J. Mihaljevic Sent: Thursday, March 19, 2009 7:51 AM To: [email protected] Subject: "Not a database file" in FPD 2.5 Hi all, Someone I know who is still using FPD 2.5 had some tables get damaged. Lots of them. And when trying to open them, we always get the "Not a database file" message. Back when I used to use 2.5, I remember this happening occasionally, and I had a PRG that fixed them. But that's long gone. Does anyone have something that can repair these tables? Some code I can run to fix them? I think he's got over 100 of them that need repaired. Thanks! John [excessive quoting removed by server] _______________________________________________ Post Messages to: [email protected] Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech Searchable Archive: http://leafe.com/archives/search/profox This message: http://leafe.com/archives/byMID/profox/014601c9a8b3$cf3996c0$6dacc4...@com ** All postings, unless explicitly stated otherwise, are the opinions of the author, and do not constitute legal or medical advice. This statement is added to the messages for those lawyers who are too stupid to see the obvious.
