Tony,

I've been running a FPW 2.6 application and have not encountered a corrupted index in about 1.5 years.

In my VFP 6.0 applications i've NEVER encountered (not that i know off) a corrupted index.

Two things to avoid corrupted indexes:
Try to open files in exclusive mode as less as possible. Exclusive access to files more often lead to corrupted indexes than shared access. If tables are opened by more than one workstation, corruption of indexes are less lightly to occur.

The reason behind this is that if one of these two rules are not met, the workstation holds a writebuffer at the client site. If something goes wrong when (or between) writing the buffers to the network/disk, the chances are that you'll end up with corrupted indexes and/or tables.

In VFP use buffering to write your changes to the table and use transactions to make it all-or-nothing. Theoreticly this would not prevent corruption when writing buffers to the network/disk. But when talking about personal experience, this seems to be quite effective

Other questions:
- Are you by any chance using a Novell network.
- I'm aware that on a NT 4.0 server adding a registry key (I forgot the exact name, should be called something like ChacheOpenLimit ? helps to prevent some problems, it should on the technet CD somewhere can anybody help me out here ?)

Which version of VFP do you use ? Which service pack ?

Walter,








>Dear All
>
>All this time I only use FP or VFP for any database application. I wonder if Database / Index File Corruption also exist in other database such Oracle and MS-SQL ?
>
>Some users blame me for using VFP when their files got corrupted. They said its my fault for choosing VFP as the database system, since according to them it's already known for a long time that VFP dbf / index is easily got corrupted. In my experience, there are sites which never got corrupted files for more than two years, but there are also sites which got corrupted files in every two days or even twice a day.
>
>Thanks in advace
>Tony Fadjar