>>>I have an application written in FPW 2.6. From time to time a table becomes damaged. When the user takes an action that requires such a table being opened in a work area, error # 15 ('Not a table') results.
>>>
>>>Is there any simple action that may be taken programmatically to restore the .DBF file?
>>>
>>>Is there already a good utility on the market that does this well?
>>>
>>>Is there a way to check for the integrity of a .DBF file in a maintenance procedure so that the problem doesn't have to be found by the user in the middle of a session?
>>James,
>>To keep it away from user seeing in the middle an error handler might be used. These type of errors generally is a result of wrong reccount() info in header. Without exclusive access it can't be corrected on site (typically you would have exclusive access to such a table). But I think keeping the repair process as a separate app is better. I'll mail you my own routines (as legal stuff - use at your own risk and read out the details). BTW if this is Novell (where I have encountered most, try setting TTS on). Good luck.
>>Cetin
>
>Cetin,
>
>Thanks for the tip.
>
>I have been asked to develop an utility to perform maintenance on the tables which are accessed by the application mentioned above. I'd certainly appreciate an opportunity to look over any code you would care to send me. My e-mail address is james@datasmith-cs.com.
>
>The application is running on a Novell Netware 4.0 network.
>
>James

James,
Nothing against what Cetin has done, but I would suggest getting a copy of Stonefield's toolkit.. It will handle problems with tables and rebuild indexes for you you a lot easier.. The code has been tested by a few people and is sold to you with the product..