I found the problem.

The situation was this, a record was added to a view and the primary key was
not updatable because the base table hade an update trigger where this was
handled. When this is the situation, once a TABLEUPDATE is enacted, any further editing will cause the record to be deleted upon the next TABLEUPDATE.
My sub editing screen had a GOTO (Passed record #), this forced a TABLEUPDATE to occur. Then editing took place and another TABLEUPDATE upon the save. This second TABLEUPDATE caused the record to get marked for deletion in the veiw.
Making the primary key updatable took care of this.

Thanks to all who responded
Chris



>
>>I have form with, buffering set to 2, that contains a read only grid with an updateable view as the record source and record source type set to alias .
>>When a command button is pressed, a record is inserted into the view and a sub-editing screen is called. In the second form textboxes and combos are bound to the view and used to get user input.
>>A command button is then used to either TABLEUPDATE or TABLEREVERT.
>>Intermittently, issuing a TABLEUPDATE(.T.,.T.,”lv_details”) causes the view new record to become deleted in the view.
>>
>>Any ideas?