I've got the following situation:

1) Web based entry form w/ grid that has updatable fields - must keep this interface. The grid data is child data.
2) Passing data from ASP page, to VFP business object for validation. Data is passed in an ADO-like array. (rather than ADO RS, per MS suggestion)
3) The child data may include new records, updated records and records flagged for deletion.
4) For the majority of screens that work this way, child data would be fewer than 10 fields, and fewer that 20 rows.

Here's the question:

Would it be better - from whatever standpoint (design, i/o, etc.) - once the validation is passed to handle the actual data modifications...
1) .. one row at time, performing the appropriate action for each. i.e., update row 1, delete row 2, insert row 3, etc.
2) .. by deleting all related child data, and inserting the given data.

The backend would be Oracle.