>>forgive such a basic question but i am new to the MM way of
>>handling data ; i am a single tier dinosaur
>>
>>what are the reasons for placing an index on a view
>>versus the reasons for placing an index on a table ?
>>
>>i think that indexes are made on views for keeping the data DISPLAYED in a specific order
>>
>>whereas
>>
>>an index on a table in a database is used for these reasons
>>1. primary id of a table for all sorts of basic housekeeping reasons
>>2. DELETED() for rushmore optimization
>>3. allowing relations to exist between TABLES
>>4. speed up the query portion of a parameterized view done on the table ... if the table is large ..
>>
>>and i think
>>this is why one may encounter an index on a table that is identical to an index on a view of that table ?
>>
>>am i missing anything here ?
>>
>>TIA, Dave.
>
>David,
>You're right. And if you need only a certain order for you view, you could as well use the ORDER BY clause of the SQL statement. Also bear in mind that table buffered views need to have their buffering changed to record buffering before you can index them.
>
>José

Jose,

The ORDER BY is great for displaying a view, but if you add a record, it is displayed at the end of the view. To get it to display in the expected position, you need an index.

Just my $0.02

Rex