Terry,

Your thread title says indexes but your thread body says tables. Which is it?

What do you mean by "via the web"?... As a single web transaction or FTP or XML or???

You say "due to any number of reasons...". What are some of those reasons (it can help people come up with answers if we know the nature of the problem)?

Are you using BEGIN TRANSACTION at all? Is any table key INT and at the beginning of a table's data? What is the average number of records per update?... where corruption occurs?


>What is the best way to determine if a table has a corrupted index?
>Can this be determined without doing a seek?
>
>I am performing a replication of data from one database to another database remotely. I am not using remote views, but going directly against the tables at the remote site via the web. Due to any number of reasons, the tables are getting corrupted. Thus the next time replication occurs, the update fails.
>
>Would using remote views be wiser?
>
>Short of going to SQL, is there anything that I can do to reduce the occurrence of this index corruption?
>
>BTW, one of the tables is getting quite large, 800,000 records with indexes.
>
>Thanks