Charli,

In general you don't want to do this. If creating a compound index, you must be sure that the child table is available and the relation set in any case when the index is adressed. When using a *.idx index or compact index, you must be aware that other users on the network can corrupt your index by modifying the fields without updating the indexes.

It might be better to use SQL-views in this case. Thought they are slower, you can index them without having to worry about the multiuser environment, relations etc..

Walter,



>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