>In these cases, I have a non-updatable view to use in grid for the user to select a record to edit. In this view is also the PK field. I then call my editing form and pass the PK of the record selected [actually I store this value to a global app object property]. The editing form using a 2nd parameterized view with all the fields needed for editing. The parameter used is the PK I just stored in my goApp object property.
>
>The advantage of this is that the lookup form contains a minimum of fields in the view in order to select a record. The updatable view has only 1 record but all the fields needed for editing. This keeps the form performing [loading] as quickly as possible.
>
>As for the update form, I also have code in the Activate to check if the PK value stored in the goApp property has changed. If it has, I issue a TableUpdate on the current record, then do a REQUERY() of the view to get the data for the newly selected record. I am using NON modal forms with private DS to do all this. This allows the user to switch between the 2 forms selecting different records to edit without having to close the editing form first.

Bingo! I was thinking way too hard about running one off of the other it didn't even occur to me how clean it would be to have the first one non-updatable and the second one doing the updates - exactly where you would want it to be! That fits perfectly into what I'm trying to do... Thanks! Renoir