>>AutoInc clashes with Table buffering applied on parent table. One may rethink interface to avoid these cases.
>
>The only other way (besides the kludge approach I already thought off) I see is to not allow to enter children unless we saved the parent.

I think you exaggerate. Frankly, I never get in this situation (generally speaking I don't use Tableupdate, except special cases), but why do you need to have table buffering on parent? You could have row buffering and go by each record, saving parent record, getting Id, and then saving child records.