Leemi
Mon Aug 04 12:46:39 CDT 2003
Hi Carlos:
There is not an automatic way of detecting this corruption. The best
advice I can offer is to recreate the indexes each time you start the
application. However, I realize if the tables are very large this can take
too much time.
If the time needed to recreate the indexes each time you start is
prohibitive, then you could use an ON ERROR routine to trap for various
index errors, like "Index does not match the table. Delete the index file
and re-create the index" or "Index tag is not found," and then perform your
code to recreate the index files.
I hope this helps.
This posting is provided "AS IS" with no warranties, and confers no rights.
Sincerely,
Microsoft FoxPro Technical Support
Lee Mitchell
*-- VFP8 HAS ARRIVED!! --*
Read about all the new features of VFP8 here:
http://www.universalthread.com/VisualFoxPro/News/VFP8Release.asp
Purchase VFP8 here:
http://shop.microsoft.com/Referral/Productinfo.asp?siteID=11518
Keep an eye on the product lifecycle for Visual FoxPro here:
http://support.microsoft.com/default.aspx?id=fh;[ln];lifeprodv
- VFP5 Mainstream Support retires June 30th, 2003
- VFP6 Mainstream Support retires Sept. 30th, 2003
>Hello Group,
>I wonder if there is a way to detect index corruption at run time. I want
to
>detect corruption when my app is lunched so I can fix it and avoid
>subsequent troubles and error messages presented to the user.
>I appreciate any help in the subject.
>TIA
>Carlos Jones