> Without an alternative explanation and since the daily rebuild
> prevents the problem I still have to assume corruption is the cause
> and continue with the rebuilds.
>
> Matt
>

Did the PLAN indicate that the same index was used for both the select
and the update? If so, a corrupted index would not have caused it. If
(in your test environment), you slightly manipulated the queries so
the no indices are used (eg, add +0 to the fields in the where
clause), are the row counts still wrong?

Do you have any update triggers that might (directly or indirectly)
deleting or inserting records thus effecting the counts?

Adam