In a similar scenario, I create a cursor with a lot of empty records, which my customers fill with data from a grid. When they are finished, I process the data in the cursor and add all not empty records to my real table, using !EMPTY(). Works like a charm.

>Seems silly.
>
>My basic form checks if data has been changed, (append, delete, fields edited and so on) and sets a bunch of stuff to enabled / disabled accordingly. I really don't want the user to have to press a Revert button, just because they happen to land on a master record with a corresponding empty grid.
>
>If that's the only solution I guess I'll stick to the button concept.
>
>Different suggestions are still welcome :-)
>
>
>
>>Always start with a blank record....
>>
>>>Short of putting a button on the form in order to add the first row, how can I implement down press on an empty grid.
>>>
>>>BR and TIA