>>Sometimes the view builder does a poor job of setting up the view code. Now that you've got the code, why don't you use it. Make the change as I've done below making all the fields updatable.
>>
>>
>>Dan
>
>I do use the code to set up the view. And I changed it to allow the key to update. However I still get an "Update Conflict" when I close the form.
>
>To Summerize :
>
>I have a one to many relationship, many records displayed in a grid.
>
>Container for the many grid includes a button to edit the many records.
>
>Pressing the button brings up a SubForm showing the selected or first many record. The form data comes from a local view of all of the many records assigned to the current one.
>
>When I push the "add" button off of the tool bar I can fill in the subform and save it. I have confirmed that the change is made to the local view and to its source table.
>
>When I try to close the SubForm I get an "Update Conflict" message. If I suspend the operation and try to browse the local view I get the same "Update Conflict" message.
>
>The subform is marked Default Data Session so the local view is in the same data session as the tables from the main form.
>
>I still do not know what is causing this.

Ok. Had to go back. The code you should me had one problem. The key field was not updatable. You have to change the .F. to a .T. for the key field.

HTH