>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 ?

If you have people having sudden crashes, there are only a couple ways I know of to stop all index corruption:

1) Place all possible tables/structrural indexes in read/only directories. All such tables will be immune to any index corruption. This is particularly good for large, read-only tables.

2) If the tables are fairly small, you can always add local non-structural indexes as needed. This is also foolproof, but the tables must be small to not hurt performance. To not clutter the drive, you can do file checks for the index files and delete if found at startup or shutdown of app.

3) I run periodic index rebuilds at off-hours on other tables. I consider this very important, it cleanses things.

I use a combination of all these things, and rarely have problems.