Paul,
I've found I usually have most of my indexes on one field. These are used (as Mark said) for most WHERE and SEEK commands. I DO have a few in my main tables that are just for ordering and use several fields. For example I want to order a child table by PO# and by date and line # within each PO#. However, I've found that much of the 'ordering' problems are taken care of faster/smoother/easier if I use parameterized views or cursors for the data (cursors if the data won't be updated as for a report, p-views if updates are required)

My $.02 US
Barbara

>Thank you very much Mark for your response,
>
>This is kind of what I was thinking....I hadn't started out that way...I had a few indexes with many fields because I am also used to using indexes for ordering purposes.
>
>I appreciate your help,
>
>Paul Acton