Jim,

Are you in a position to disable the users' ability to choose to do an index "repair"? ...Or to tell them to call somebody rather than do it themselves? Doesn't sound like a good idea to me, at least in the general case.
Is it possible that someone is too fond of that capability and is overusing it?...Or maybe doesn't quite understand when to use it?

You say that changes are stored in arrays and you say you have locks. Are the locks placed as soon as a record is accessed, or at save time only? If the locks are early, are you confident that *all* records REMAIN locked until save time is complete? SET MULTILOCKS must be ON to lock many records in an app. at the same time.



>This is a CDX.
>
>Yes I have tried set order to tag fldsidx, and get the same error.
>
>The software is a multi-user software, so it is possible more than one person might be in the table, but we have locks and we don't have the users updating the table until a save is used. The changes are stored in arrays before save. When I am trying to fix the data, no one else is using the tables. I am on a stand a lone pc.
>
>There is a function for re-indexing the user can use if they think there might be a corruption. It deletes all the tags, and looks up the index tags in a data dictionary and re-creates them. This usually fixes problem, but in a very few cases it can break a fixed table. I can't imagine why.
>
>Thanks,
>Jim