>I had same situation and was not unable to fix it.
>Finally I started to use the following code. This adds blank rows but
>I don't see other way to fix this fox bug.
>
>proc DELETEROW
>* Delete a row in child table, callet from keypress event
>if recno()=recc()
> blank
> else
> delete
> endif
>unlock
>if !eof()
> skip
> else
> if !bof()
> skip -1
> endif
> endif
>
>>Ken,
>>
>>No the table is not buffered. I have an invoice number in the parent table that is related to the child grid rows - master-detail type relation.
>>
>>Thanks for all the help with this.

Making the grid refresh properly has also cause me quite a few headaches. I've finally settled on the following code,which is executed on clicking a command button

SELECT (childfile)
DELETE
GO TOP
SELECT (parentfile)
thisform.LockScreen=.T.
thisform.grdLineItems.Setfocus()
thisform.grdLineItems.Refresh()
thisform.refresh()
thisform.LockScreen=.F.

However this is is again not foolproof and I set grid.deletemark =.T. some the user can see that the particular record is deleted

Sonali