>>>>>>>
>>>>>>>Insert Into ViewTable1(parent_id,other_id) Values (Parent.parent_id,Other.other_id)
>>>>>>>
>>>>>>>Am I getting warm?
>>>>>>
>>>>>>Yes, and it's not my suggestion :), it's normal VFP way. The idea is that when you add record to a view, it's not in table yet, i.e. your interface can have Cancel functionality before you will issue Tableupdate() to send data changes from view to table.
>>>>>
>>>>>I changed my insert command but I still need to move the record pointer before my insert appears!
>>>>>
>>>>>TIA --lincoln
>>>>
>>>>Do you issue Grid.Refresh, or at least Grid.Setfocus?
>>>
>>>I did issue a Grid.Refresh, It is before my EndIf if it makes a difference.
>>>I also noticed I get an Update Conflict message if I try to delete a record I just inserted!
>>
>>Firstly, use table-buffered view (BufferModeOverride=5 for view). Secondly, Grid.Refresh must work, or it's something amazingly miraculous ...., you can fortify this command by Grid.Setfocus().
>
>Perhaps have I should have told you, the Refresh event of my Grid1 has the following code in it:
>
>m.cParent_id = This.Text1.Value
>=REQUERY("VTable1")
>
>The value of Text1(non-visible textbox) is equal to my Parent_id.
>The purpose of this is to set the value of my paramatized view to the Parent record as the record pointer changes with my Nav buttons.
>
>Would this make a difference?

It makes a lot of difference. Remove this requery() stuff from Grid.Refresh. Firstly, you don't need in this, and secondly it kills the whole idea of view. When you change data in grid (view), you actually write to buffer. If you issue requery(), the first thing which will be done is killing of this buffer.