>>>I don't know, really, why you have this behaviour. ...
>>
>>Perhaps you should take some steps to avoid index corruption. Mainly, IMO: 1) issue FLUSH after the TableUpdate(). 2) Disable write-cache on your file server.
>
>FLUSH would be easy, I think I'll actually try it, it's just one line to add to the class code.
>Write-cache, that's a problem, I don't know enough about our server to get into that, but our net admin is reluctant to change, the main argument being that we have hundreds of other tables and lots of apps that are OK.
>Thanks again.

My bet is that your Net Admin already has write cache turned OFF on the server.
But modern workstations running (Win2K ans WinXP at least) also have a setting for the hard drive for "Write cache". This should ALWAYS be set OFF (unchecked in the appropriate property of the hardware properties).

cheers