>>>In a network application on a Novel network the user occasionally gets the error message "Table failed to update table. Unique index viiolation:."/ Usually when trying to add data. Any idea why would be appreciated.
>>
>>Claude,
>>
>>Do you have a unique index in your table? Usually it doesn't make sense to have unique indexes, make sure you're not confusing it with the candidate index.
>
>I change a candidate index to a regular index and had to add ah explicit SQL Update command to avoid duplicating the record/ I also removed the implicit edit command from my find command so that user has to explicitly edit the record to avoid the Uniqueness violation error.
>
>I do not understand why how the one gets to the record would make a difference when it is saved.
>
>the user is testing now.

It all may depend on your design, do you use buffering or not, etc.

But you don't use UNIQUE index, correct? You should not use it, the candidate index was OK, though, to avoid duplicity (but you should trap against the other error yourself then).