>The updates are done with replace/update and not with a SQL Statement. They
>are using the ADO's recordset object to update the database (ex.: oRS.update).
>
>The tables have indexes but I will need to look into it (they admit to not
>fully grasp the Rushmore Technology). But with replace/update it should not
>impact right?

Actually, it may very well impact it. I think the Recordset.Update command builds a SQL UPDATE statement in the background, so it would be looking up values in the index to figure out what to update. (Please ignore the company name above, I'm wildly speculating here)

>Also, there was a thread (few months back) discussing replace/update VS SQL
>Update and the conclusion, that I remember anyways, is that both will work and
>it is mostly a matter of preference. I prefer Select statements, but do you
>think that it would help to use SQL statements in this situation?

No opinion here. I didn't get heavily into ADO before working here, so my experience is biased towards SQL Passthrough.