When you say "there appears to be nothing wrong with the indexes", did you actually tried to delete and recreate the index? The table may be opened without problem, but if an entry in the index is corrupt, VFP may crash only when it reach that point.

---

>I have an app for a client that is giving error 114's pretty consistently. By that I mean, it happens at least once a day, but I can not reproduce the problem.
>
>Index 114 is "Index does not match the table. Delete the index file and re-create the index." However, there appears to be nothing wrong with the indexes. The user can immediately re-enter the program and it will continue to work w/o problems, including repeating the same action that caused the error.
>
>The app opens all the files read only (no update), none of the controls are bound to fields and all fields are read only as well.
>
>There is only one app that updates the tables and it runs as a stand-alone app on a pseudo-dedicated pc.
>
>The error usually triggers on a seek, but I have seen it trigger other places as well. For example, the last error report I received showed it triggering on the initial READ EVENTS in the main PRG file.
>
>Help! I think it might be a network issue, but I need some way to verify this. The client is running Netware 4.11 and win95/98 ws.