>>>Parameterized, ordered views are the best way to go in situations like this.
>>>Something else that might work is to base the grid on a SELECT statement. If you
>>>need to edit in the grid, copy the results of the SELECT into a temp cursor. Just
>>>be careful that you don't lose the connection between the grid and the RecordSource
>>>when you do that.
>>Yup. I should have added in parameterized view, but I think that it is unecessary to use one.
>>Can you help with the problem.
>
>The SELECT statement and the p-view are the only things I can think of
>offhand that will give you your sorted table....

Garrett,

It just seems that creating a parameterized view for something as simple as displaying a child table is defeating the purpose of being able to create relationships between tables in VFP. I do use parameterized view, but usually when I create a complex relationship between a parent and several children.

Basing the grid on a select into a cursor means that I can't edit the data, it is read only. Once again this is an excellent and fast technique, but does not take advantage of the power of VFP (IMHO).

Just a note... Garrett, I appreciate your responses to my question... I am not criticising your answers, but merely stating why I can't use them or think they shouldn't be used in my circumstance.

Any other ideas?