>A system I've been working on for two years has gone live and though it's generally working well we are being plaqued with locked-up computers and occasionally corrupted data files.
>
>My system is based on Visual FoxExpress, and (wouldn't you know it) Mike and Toni went on vacation today for two weeks.
>
>In about five occasions over the past two weeks a locked-up workstation has been rebooted (or end-tasked) and the result has been to corrupt one or both of the reservation files. There are about ten main files but it always these two that get corrupted.
>
>At that point I have to get 30 users out of the system and rebuild the two files by appending from the corrupted files to a good (empty) copy of the files.
>
>I have just added a FLUSH at the end of the SAVE method of my main form class but I don't have this version up yet.

One thing that helped in DOS days was to open the same app and same form (with the same tables) on another workstation, update some little bit of something (usually deleting or adding a final period in a comment field somewhere), and then regularly closing the app. It usually caused the buffers to be refreshed & flushed on the server, and even the data from the locked station were saved (at least to some point - never paid too much attention to that). It may still work.

>I generally have most of the files open in Data Session 1 with the updates being performed in a private datasession started by a form. I usually have 3 or more forms open (all but 1 hidden) at the same time.

I think Aleksei Bulgakov has found a way to corrupt indexes if the tables were open read-only in the default datasession, and read-write in form's data session. The indexes were actually OK, except for the new records not showing in them. One thing to try is to remove the NOUP clause (or ReadOnly setting) on the tables in the DS 1, if they are set so.