> >> >> We've mentioned a several occasions that buffering is now the way to
> go
> >> >> instead of scatter.
> >> >>
> >> >> But, in the situation where the user is doing a data entry in the
> >> temporary
> >> >> table which has the same structure has the master table, and we then
> use
> >> a
> >> >> transfer button to move the record from the temporary table into the
> >> master
> >> >> table, isn't the only way to go scatter and gather?
> >> >
> >> >Why not SELECT INTO ARRAY, INSERT FROM ARRAY?
> >>
> >> Why not just scatter and gather? Is it too simple? :)
> >
> >If you are editting information in a Grid, then you'll have to
> >scatter/gather for each row. SELECT/INSERT will work regardless if 1
> >record or n records.
>
> This is Michel's original message:
> <
temporary table which has the same structure as the
> master table, and we then use a transfer button to move the record
> from the temporary table into the master table, isn't
> the only way to go scatter and gather?>>
>
> and it's clear about *the record*, not about n records. The problem was to
> edit one record in a temporary table and then to move it to the permanent
> one.
>
> Would you recomend SELECT/INSERT for very large databases also?
I suggested SELECT/INSERT as one possible alternative, not necessarily
as the best or only alternative. Then I justified the suggestion. I
was hoping not to have to defend the suggestion, but that's what you
seem to want. I apologize, but I will not oblige this.