ForeHead.Slap()

>Oh. OK....a viewpoint difference. I didn't mean to imply a TABLEUPDATE with every record delete....just at some point before the master record is updated.
>
>>
>>Making a TABLEUPDATE() after every delete means that the data cannot be reverted. If the design requires it, then its ok. In most cases, it is better to let the user choose Save() and then only update the data.
>>
>>>Why not? Now I'm confused. One of the lesser known facts about VFP is that you have to update base tables with deletes. I have worked time and time again with table buffered child tables and have found a TABLEUPDATE to be required.
>>>
>>>With row buffering....I dunno....grids don't allow row buffering easily.