Your question has a wide scope and depends on software and hardware issues. An unreliable network can cause corruption, as can power outages, etc. However, from the software side:

Try not to leave all databases/tables open during full duration of program if not required. Use only those needed for each Form and close them on exit...

Take a close look at your most active Table(s), those getting the most updates. Try to Close/Tableupdate()/FLUSH them often as Hilmar said...

Definitely use the features of the DBC as well as Buffering at some level, it works well...

Perhaps if you can capture the error and issue CLOSE ALL or something similar it would help to try to insure all tables close, but that is difficult to do in a corruption circumstance...

HTH,

-Irv.

>i have a program that manages a cyber coffee. this program is used on many computers at the same time.
>some time the program craches cause of index corruption and afterwards foxPro will cause fatal error.
>To solve this problem, i stop the program on all computers, i reboot the computer where are the tables and i reindex all tables.
>this procedure is too long and not interesting.
>
>what can i do to avoid index corrution problem ?
>
>i reboot the computer because some time the tables are not close so it is difficult to reindex.
>what can i do to force tables to be closed ?