>>How would you do this if the backend was SQL Server or Oracle? Even when I use VFP as the backend, I have started asking myself this question and design that way [just in case the project eventually ends up as C/S].
>
>Well, that what was why I prefaced this with "this is for native tables". I dunno, but I probably would have to granulate the saves/reverts.

I'd advocate smaller granularity, because the validity of edits against one subentity are not really interdependent on edits of changes made to another subentity, so the granularity of tableupdate/tablerevert is an issue here. This is one place that drilldown pays off well, because at least in theory, the edits of one subentity's data can be done in a distinct p-view instance from the edits of another, and so the granularity problem isn't a problem...