>>>>You could use parameterized table-buffered view as Grid.Recordsource. Then you use CALCULATE SUM... from Grid.Column.Text.InteractiveChange event, assuming that you will restore record pointer.
>>
>>>Edward,
>>>
>>>I haven't tested this, but if you are using a view can't you just run another aggregating SELECT against the view to get column sums? You wouldn't have to save/restore record pointers that way.
>>>
>>
>>The problem here is that Select-SQL will go to the underlying table ignoring interactive changes (no tableupdated yet) in grid.
>
>You can
>Select * from myview
>instead of
>select * from underlyingtable1, underlyingtable2
>
>and the results will show the data from the view, updated or not.

It was discussed initially few months ago, and it was settled that Select-SQL will go to the underlying table anyway, doesn't matter what is written in FROM clause.
To make this sure, I just tried quick test, and results are still the same: it's going to the table, and if no TABLEUPDATE() issued yet, then result misses interactive grid changes.