I guess not in the dialog pop-up, but here's the help entry for 2091: Either the table record count does not match the actual records in the table, or the file size on the disk does not match the expected file size from the table header. Repair the table using an appropriate third-party repair utility for Visual FoxPro tables before opening the table again.
-----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of MB Software Solutions Sent: Tuesday, January 30, 2007 11:21 AM To: [EMAIL PROTECTED] Subject: Re: Corrupt Table Lew Schwartz wrote: > Along with the buffer overruns, the crashes leave a number of > corrupted tables which can't be opened without being reminded about > 3rd party repair utilities. It seems that set tablevalidate to 0, use > excl, pack, use, set tablevalidate to 3 works too.... So what's with > the 3rd p utils? Or am I wrong? > Does it actually tell you to use 3rd party utils? -- Michael J. Babcock, MCP MB Software Solutions, LLC http://mbsoftwaresolutions.com http://fabmate.com "Work smarter, not harder, with MBSS custom software solutions!" [excessive quoting removed by server] _______________________________________________ Post Messages to: ProFox@leafe.com Subscription Maintenance: http://leafe.com/mailman/listinfo/profox OT-free version of this list: http://leafe.com/mailman/listinfo/profoxtech ** 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.
