Jon

>The goal is to improve the performance of some very slow REPLACE, SELECT, and LOCATE statements whose performance is terrible on these large tables. The methods that I'm trying to improve performance on are preexising and I'm not trying to rewrite them..I'm just trying to speed up the slowest parts of it and indexes seemed the natural way to improve the performance.
>
>As far as the real reason behind using such a large index..I have various information during various parts of the program and thus need to find a way to "search" through the views on different criteria...

I understand that's your hope. Please recognize that the fastest solutions can only be offered if we have a complete understanding of the scenario.

I don't know why you'd want to build an index across multiple tables adding together the various primary keys. If you could explain the purpose of the code, that would help. I find it quite common that re-engineering is often the fastest solution.

A query may be a better way to go than adding another index, but at this point, I can't say.