>Hi:
>
>If you want to index a child table engaged in a relation, what is the best way to do so and preserve your foreign key? For example, if your child table is indexed on a foreign key (integer), but you want to physically order your table on another field, say last name (char), how would you create this sort of compound index?
>
>Thanx,
>Charlie

I have done this in the past by:

First I have a child view that would be set up on a view parameter of the parent key. Then I would order the view by what how I wanted child data displayed.

You could also just set up a view on the parent key and then order the view any way you wanted it inside the application.