>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 ?
You should issue the command FLUSH after changing records - if you use buffering, after TableUpdate(). This reduces corruption significantly.
Difference in opinions hath cost many millions of lives: for instance, whether flesh be bread, or bread be flesh; whether whistling be a vice or a virtue; whether it be better to kiss a post, or throw it into the fire... (from Gulliver's Travels)