For your child records, you want a *parameterized* view.

Set the parameter to be the parent primary key, and then Requery() when the parent record changes. You'll always be displaying only the records that match the current parent record, so no need for relations or filters.

Dan

>Hi all,
>
>I'm having the following problem when using views in one-to-many forms: instead of the child table I use a view, but in order to establish the relationship between the parent and the child table I have to index the view.
>
>Problem arises because I cannot index the view because is in buffer mode (all my forms are buffered). If I don't use buffering at all, I cannot use tableupdate() and only the last record updated in the view can be saved-unsaved. If I try to unset buffering, index, and then set again buffering on it says me that "this configuration will take effect next time you load dataenvironment".
>What I'm doing now is filtering the view to match the ID in the parent table, but I think it should not the right way to go (it is slower and the scroll bar does reflect the whole view, not just the matching records).
>
>I'd appreciate some light on this, and would like what are you doing to acomplish this, as it might be a common topic.
>
>Kind regards,
>Javier Borrajo.