Hi Ken ---
Is there any way to reduce the number of indexes? An index on every field?? Ouch. You might want to consider doing some research on data organization and indexing as pertains to data warehousing. Data warehousing techniques and theory may help you find a better way to manage and organize the data.
Perhaps, also, you could spawn several child tables that offload data from the main and maintain separate indexes for each. You could monitor data changes and then do logical reindexing.
Since I don't know what you're storing and how, I can't get more specific.
>I have several tables of 1 million+ records that are frequently replaced in their entirety. When this is done, they are all indexed on every single field.
>
>In one instance, indexing a 1 million record file on 183 fields can take from 5 hours (process running on server) to over 15 (over crowded LAN).
>
>I thought: Wouldn't it be cool to have a multiple key indexer that reads records only once and builds multiple keys as it goes, allowing only a single pass through the file which results in a complete CDX.
>
>If, by any stretch, someone has something like this, please let me know. If anyone else has the same need and would like to collaborate on getting it written, let me know also and we'll see if we can crack it.
------------------------------------------------
John Koziol, ex-MVP, ex-MS, ex-FoxTeam. Just call me "X"
"When the going gets weird, the weird turn pro" - Hunter Thompson (Gonzo) RIP 2/19/05