Views are just temporary holders of data. The control achieved in sorting, excluding and such are worthy of maintaining in your data manipulation sessions.

I use views for everything. I index them in the same method as page 158 of the 4.1 manual. That's the CGrid class and how to change sorts via clicking on the column header.

It's also necessary to use these in your FIND forms.

__Stephen Russell


>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.