Since your view probably has all the fields that are being updated on page 2, I would say 1 view. However, I usually have 1 cursor and 1 view. The first view is the pick list and is not updatable and has a limited number of fields. I allow my users to input values for specific fields then build a query to select the matching records into a cursor. They select a record to edit from the cursor which is displayed in a grid on a SQL results form. This form then calls [from a command button] the edit form. I have a goApp object property where I store the KeyID of the selected record. The value of this property is used in the child form [in the activate method] to REQUERY() the view which, of course, will contain exactly one record.

>Good morning,
>
>I have forms, w/a page frame, where:
>
>- the first page displays a list of entries (in a non-updateable view); the user can select an entry and view/modify it on the second page
>
>- the second page allows the user to add, delete or modify a single entry via an updateable paramatarized table buffered view
>
>Right now, when changes are made on the second page, the view on the first page is REQUERYed (i'd previously looked into using the VIEW REFRESH() function, that "updates one or more records in a view with the current data from the original data source", but had trouble).
>
>Now I'm thinking, why not use one updateable view for both pages?
>
>Somehow, I felt more "sure" of what was happening, w/only one record in the the updateable view...but now, I'm thinking that it would be faster/simpler to use only a single view.
>
>Any opinions to share? (opinions? on the UT?) TIA, J