Elgin,
There are several ways of accomplishing what you want. If you want to use views, then you don't need to set a relationship from one to the other. Instead, requery both views on the CUSTID entered by the user. I'm assuming they will get one record from the parent table and several from the child table.

If you DO want to set a relationship, then you can index the child view just like any other table. Since views are always Exclusive to the user who created them there won't be any problem with creating an index on the fly.

And if you are using parameterized views, you can set the "NoDataOnLoad" property to TRUE and not have to worry about parameters when loading data.

HTH
Barbara

>I have a form that has two FP 2.6 tables related on the CUSTID field as the Dataenvironment.
>
>This form also has a container "cntSearch" with a textbox. Initially the container is NOT visible. I have a Search button to make the container visible. I would like the user to be able to type a new CUSTID in this container's textbox and when the container loses focus set the Filter property of Cursor1 to the value typed in the text box. Or even have multiple text boxes in this container to set the Filter on any or all of the Cursors in this dataenvironment.
>
>I know I should probably be doing this with Views in the Dataenvironment, but I do not understand how to relate two views in the Dataenvironment. Remember the underlying tables are FP 2.6 tables and I cannot change there format to be part of a VFP database. The relationship between the two tables has to be a One-To-Many.
>
>The performance of the form is working well as it is now with the Tables being the Dataenvironment, but I need to be able to Filter by CUSTID and sometimes other fields in addition to CUSTID.
>
>Thanks for your help. Thank God for the Pros.
>
>Elgin
>
>Epic Solutions.