>>For lots of replacements, the manuals suggest erasing the index, and re-creating it. However, this may be impractical if you update a small percentage of the records (which may still be many records!), or if the records are part of a FK.
>
>For that, you require exclusive use of the file. This is not practical in most situations.
Yes, that is an additional inconvenience, which I was forgetting.
The problem is, when you update a record, all indices are updated as well. It doesn't seem easy to design the product in a way that would somehow bypass this.
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)
