I used to have some corruptions with VFP 3, especially on Win95 peer-to-peer LANs or Novell LANs. Since VFP 5 I have not encountered a single index corruption in normal day-to-day use unless something dramatic happened, like a PC was turned off in the middle of a diskwrite.

You can 99.99% eliminate index corruptions by moving your data to SQL Server, but then you have other issues to contend with.


>I only have a few installations with VFP. I occasionnaly have problem with index but not too many.
>Nevertheless, I am confronting some people right now that tell me that they definitely don't want fox around because they used to have a lot of indexes problems ("Always corrupted...","...have to reindex every days...", and so on...
>I don't know what to tell them...
>Is it true ? Is there particular situations where there are more chances to get corrupted indexes ? Is there any ways to avoid corrupted indexes ? How frequently do we have to run reindexes ? How can we tell when to run reindexation (before errors occurs) ?
>Do we have less chances corrupting the indexes if we update with SQL commands ?
>
>Is it why a lot of people are going the client-server road ?
>
>
>Thanks for any comments on this.
>
>
>Eric